Eugene Kuleshov wrote:
> 
> Stuart McCulloch wrote:
>> FYI, the approach used in Pax-Construct is to unpack the embedded
>> dependencies under the target folder, and then refactor the bundle
>> manifest when it's copied to the project root, so the Bundle-ClassPath
>> points to the right jarfiles in Eclipse/PDE
>>
>> For example:
>>
>>    Bundle-ClassPath: .,kxml2-2.2.2.jar
>>
>> is transformed (in the Eclipse/PDE generated manifest) to:
>>
>>    Bundle-ClassPath:
>> .,target/pax-eclipse,target/pax-eclipse/kxml2-2.2.2.jar
>>
>> You can try this out by downloading the scripts...
>   Stuart, out of curiosity, why didn't you provide Maven archetype and 
> plugin with additional goals instead of creating proprietary scripts 
> that require manual install?

Hi Eugene,

actually it does use standard Maven archetypes and plugins underneath,
which you can also run using the Maven command line without requiring
the scripts at all.

the scripts provide the following additional features:

1) initial bootstrapping of the plugin and archetypes, because they
   are currently deployed to the OPS4J Maven repository, not central
   - otherwise users would have to remember the long form of the
   plugin command (with groupId, version, etc, etc.)

   ( this is done by using Maven to detect the plugin is not in the local
      repo and then forcing a "mvn -U ..." with the complete details and
      the right version to pull in the right plugin )

2) shorthand syntax for commonly used commands (ie. -g for -groupId)
     with context help for each command - and if you type the command
     and miss out mandatory parameters it will prompt you for them with
     suggested default settings

the final result of each script is a single "mvn ..." command line which it
then executes (btw, the windows and unix scripts are generated from a
template).

these scripts were developed from user requests + feedback to "ease
the pain" wrt. remembering commands and getting the plugin installed

btw, once you've created your project and bundles then it's just like any
other Maven2 project - you don't need the scripts to build or deploy it


Eugene Kuleshov wrote:
> 
>   regards,
>   Eugene
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 

-- 
View this message in context: 
http://www.nabble.com/osgi-embed-feature-m2eclipse-plugin-tp13666172s177p14591176.html
Sent from the Maven Eclipse - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to