search

sakella6669 / iaml

Automatically exported from code.google.com/p/iaml
0 stars 0 forks source link

Put third party sources into separate plugin #49

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What new or enhanced feature are you proposing?
Currently, sources for projects and plugins used within IAML are not
defined anywhere, and as a result there are .classpaths like so:

<classpathentry exported="true" kind="lib"
path="lib/drools-compiler-4.0.7.jar"
sourcepath="C:/source/drools-4.0.7-src.zip"/>
<classpathentry exported="true" kind="lib" path="lib/drools-core-4.0.7.jar"/>

One solution is to put all the sources used into a separate project. If the
source is an existing Eclipse project somewhere online, it should be loaded
into the Eclipse environment and referred there instead.

What goal would this enhancement help you achieve?
Easier to develop IAML in a distributed fashion.

Original issue reported on code.google.com by soundasleep on 29 Jun 2009 at 5:11

GoogleCodeExporter commented 8 years ago 
Also look at using the SpringSource Bundle Repository:
http://www.springsource.com/repository/app/

Original comment by soundasleep on 4 Aug 2009 at 4:53

GoogleCodeExporter commented 8 years ago

Original comment by soundasleep on 15 Sep 2009 at 8:17

GoogleCodeExporter commented 8 years ago 
moving all unresolved 0.5 issues to 0.6

Original comment by soundasleep on 17 Apr 2010 at 6:58

GoogleCodeExporter commented 8 years ago 
mass tagging old issues to future work

Original comment by soundasleep on 26 Sep 2011 at 9:54