I don't have a solution for you, but as you've not received an answer from
anyone else I wanted to reply.
I have run into a similar situation with aop, but haven't really come up
with a good solution. In my case, the aop weaving was just used for testing,
so the dependency tree wasn't an issue for
On 05/12/2010 7:09 PM, Brian Topping wrote:
On a related note, can anyone summarize what the best way of maintaining
eclipse projects from Maven is? I use IDEA, and the best way from there is
IDEA itself, not with the IDEA plugin for Maven.
Is the same true for Eclipse that the IDE plugin for
Some typo on my last message. The plugin causing problem is
plexus-compiler-eclipse.
On Mon, Dec 6, 2010 at 1:12 AM, Rice Yeh wrote:
> Hi,
> I just find a bug in plexus-compiler-plugin. All classes complied by
> plexus-compiler-plugin will get 'source not found' problem in eclipse class
> file
On a related note, can anyone summarize what the best way of maintaining
eclipse projects from Maven is? I use IDEA, and the best way from there is
IDEA itself, not with the IDEA plugin for Maven.
Is the same true for Eclipse that the IDE plugin for Maven is better than the
Maven plugin for
On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland wrote:
> Hi all,
>
> Does anybody know in which version the support for wtp 2.x was added?
Not really, you'd have to trawl through the code base to see for sure.
http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists
the versions availa
Hi,
I just find a bug in plexus-compiler-plugin. All classes complied by
plexus-compiler-plugin will get 'source not found' problem in eclipse class
file editor which is opened when you access the jar file containing the
compiled classes even though you have source jar associated with the jar
fil
I only look at user list infrequently. This question would have likely been
answered faster on the dev list. You might want to look at the new
maven-site-plugin and ask Olivier Lamy specifically how he's manipulating
configuration before the execution of a plugin. We also use this technique in
Hi all,
Does anybody know in which version the support for wtp 2.x was added?
And when will support for wtp 3.x be added?
Thanks!
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 219
I can't answer your question, sorry. Maybe you should post this at the
dev list. There resides the most people with intimate knowledge about
Maven's plugin setup.
With regards,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Sat, Dec 4, 20
where is your pom.xml?
C:/Documents and Settings/xname/My Documents/maven/mrt/storage ?
regards,
Hervé
Le samedi 4 décembre 2010, dloy a écrit :
> I'm a new to maven. I've recently tried unsuccessfully to get
> to work unless the absolute file path was given.
>
> I'm running on windows XP, wit
Thanks Kristian,
i will try this on monday :-)
S.
Somehow this sounds like the notorious
http://jira.codehaus.org/browse/PLXCOMP-149 and the attached
http://jira.codehaus.org/browse/MSHARED-148
Upgrade all your plugins to the latest version.
Kristian
Make sure
fr., 03.12.2010 kl. 20.47 +0
I'm a new to maven. I've recently tried unsuccessfully to get
to work unless the absolute file path was given.
I'm running on windows XP, with netbeans IDE 6.8 supposedly using maven
3.0-SNAPSHOT.
I've tried:
C:/Documents and Settings/xname/My
Documents/maven/mrt/storage/store-conf/mrt.loca
Hi,
To whom it may concern I would like to update that I seem to be able to work
around this issue:
In the super pom for all of our projects I've defined the following:
...
com.amazonaws
aws-java-sdk
1.1.0
commons-httpclient
commons-httpclient
3.1
commons-logging
commons-logging
1.1
No Maven committers reading this list? Even a "No" would help.
Cheers,
Peter
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3292542.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
Is there a way to declare that my plugin doesn't work with Maven 3? If not, how
can I handle this programmatically? In other words, how can I find out which
version of Maven my plugin gets run with, so that I can throw an exception?
Cheers,
Peter
---
15 matches
Mail list logo