m2eclipse and unpacking dependencies
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
m2eclipse and unpacking dependencies
by Stevo Slavic
::
Rate this Message:
Hello m2eclipse users,
In a multi-module project I've configured several modules to unpack their dependencies, only ones with specific groupIds. Command line maven 2.2.1 build unpacks only those dependencies matching specified groupIds. In eclipse I have m2eclipse 0.9.8 installed, and same maven 2.2.1 installation is configured as default. When eclipse rebuilds module projects I've noticed that it spends awfully long time on project validation, and when I better looked what is being validated I've noticed that it was validating files from unpacked dependencies, but instead of having only dependencies with specified groupIds unpacked, it seems that all module dependencies get unpacked. I'm not sure why this unwanted behavior happens, but I'm suspecting that this is a bug in m2eclipse. I'm aware that unpacking dependencies isn't best practice and isn't being used frequently. I couldn't find related issue in m2eclipse JIRA. Has anyone experienced any similar behavior? Regards, Stevo. |
|
|
Re: m2eclipse and unpacking dependencies
by Igor Fedorenko-4
::
Rate this Message:
Can you try latest 0.9.9 dev build?
-- Regards, Igor Stevo Slavić wrote: > Hello m2eclipse users, > > In a multi-module project I've configured several modules to unpack > their dependencies, only ones with specific groupIds. Command line maven > 2.2.1 build unpacks only those dependencies matching specified groupIds. > In eclipse I have m2eclipse 0.9.8 installed, and same maven 2.2.1 > installation is configured as default. When eclipse rebuilds module > projects I've noticed that it spends awfully long time on project > validation, and when I better looked what is being validated I've > noticed that it was validating files from unpacked dependencies, but > instead of having only dependencies with specified groupIds unpacked, it > seems that all module dependencies get unpacked. I'm not sure why this > unwanted behavior happens, but I'm suspecting that this is a bug in > m2eclipse. > > I'm aware that unpacking dependencies isn't best practice and isn't > being used frequently. I couldn't find related issue in m2eclipse JIRA. > Has anyone experienced any similar behavior? > > Regards, > Stevo. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: m2eclipse and unpacking dependencies
by Stevo Slavic
::
Rate this Message:
Updated. Just to report that as soon as eclipse started up, welcome comity was there:
"An internal error occurred during: "Updating indexes"." java.lang.NullPointerException at org.maven.ide.eclipse.internal.index.NexusIndexManager.updateIndex(NexusIndexManager.java:938) at org.maven.ide.eclipse.internal.index.NexusIndexManager$2.run(NexusIndexManager.java:546) at org.maven.ide.eclipse.internal.index.IndexUpdaterJob.run(IndexUpdaterJob.java:70) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Will report back on that unpack dependencies issue. Regards, Stevo. On Wed, Oct 7, 2009 at 3:53 PM, Igor Fedorenko <igor@...> wrote: Can you try latest 0.9.9 dev build? |
|
|
Re: m2eclipse and unpacking dependencies
by Stevo Slavic
::
Rate this Message:
Current m2eclipse 0.9.9.200909092308 works well with unpacking dependencies.
Regards, Stevo. On Wed, Oct 7, 2009 at 4:28 PM, Stevo Slavić <sslavic@...> wrote: Updated. Just to report that as soon as eclipse started up, welcome comity was there: |
| Free embeddable forum powered by Nabble | Forum Help |
