Someone please help me from navigating through the forest of no return,
that is Google, and tell me how to force our projects back to using the
older 1.2 version of the Versions plugin, instead of this newer 2.0
version which is now giving us null pointer exceptions with this simple
command:
mvn org.codehaus.mojo:versions-maven-plugin:1.2:set
/Anders
On Wed, Nov 28, 2012 at 9:04 AM, Wheeler, Dennis
dwhee...@cobaltgroup.comwrote:
Someone please help me from navigating through the forest of no return,
that is Google, and tell me how to force our projects back to using the
older
2012/11/28 Barrie Treloar baerr...@gmail.com:
While trying to sort out
http://maven.40175.n5.nabble.com/Retrieving-the-project-source-directories-from-MavenProject-td5733602.html
I was hacking his code and found that
Java 1.5 @Component MavenProject returns null
But when I changed it to use
Hi
Do you know that NetBeans has its own maven on board?
C:\Program Files\NetBeans 7.2\java\maven\bin
Your EXTERNAL maven - pointed to by MAVEN_HOME or M2_HOME might work nicely,
i.e. USE $ mvn -version
as a always first to check and tell us a bit more about what you have.
In order to
To add a dependency to my pom.xml, usually, I google the artifact, class,
jar and then go to http://mvnrepository.com and try luck by searching key
words, however sometimes it takes too much time, or I get stuck.
So the question is, is there any formal/structured procedure to find
These escapes would work in bash, but Windows batch interpreter uses ^
character for escaping, and ignores double backslashes. Additionally, in
Windows you cannot set variables with VAR=VALUE syntax. What is the interpreter
this command is being passed to? Do you run it in Cygwin bash?
Kind
Can you please raise a JIRA for the NPE
On 28 November 2012 08:04, Wheeler, Dennis dwhee...@cobaltgroup.com wrote:
Someone please help me from navigating through the forest of no return,
that is Google, and tell me how to force our projects back to using the
older 1.2 version of the
Hi all,
With Maven (3.0.3), I can generate a ZIP file containing some resources
from my projet, with maven-assembly-plugin and an assembly.xml descriptor.
OK.
I can also generate 2 different ZIP files with 2 executions binded on
different phases. OK.
Now, I need to generate the second ZIP file
Can'y you use a fileset with directory element being to your project output
directory, it should include the first ZIP file, no ?
Jeff
On Wed, Nov 28, 2012 at 2:39 PM, Xavier NOPRE xno...@gmail.com wrote:
Hi all,
With Maven (3.0.3), I can generate a ZIP file containing some resources
from
General rule - one artifact from one project.
First get your zip with a zip included, working by doing it the Maven way.
Then see if it is worth optimizing the process.
Ron
On 28/11/2012 8:42 AM, Jeff MAURY wrote:
Can'y you use a fileset with directory element being to your project output
You're not the first people to complain about this. I believe I filed
a JIRA. Let me see if I can stir up action.
On Wed, Nov 28, 2012 at 8:51 AM, Aliaksei Lahachou
aliaksei.lahac...@gmail.com wrote:
Hello everyone!
release:prepare/perform creates release only from HEAD revision and I can
Hello,
I'm not sure what exactly you need, but here's a couple of guesses:
1. If you want to copy files from the project to another location, you may
try resources:copy-resources [1].
2. If you need to load properties from properties file, you may try
build-configurator-maven-plugin [2].
[1]
I don't feel he is not following the Maven way if the first ZIP is not
attached to the project
Jeff
On Wed, Nov 28, 2012 at 2:50 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
General rule - one artifact from one project.
First get your zip with a zip included, working by doing it
Using an old copy of the libraries should work for you.
(I have packaged the following dependencies:
* jargs:jargs:1.0
* org.apache.xalan:xalan:2.7.1
* org.opensaml:openws:1.2.2)
it applies to compile axis2:1.6.0
_m2_repo.rar http://maven.40175.n5.nabble.com/file/n5733969/_m2_repo.rar
--
Hi Jeff, Ron, and other !
Yes, I had tried to use a fileset with directory. It did'nt work. But I had
some mistakes, like ${project.build.outputDirectory} instead
of ${project.build.directory}.
I have found a solution on this way. I put it here if it can help anybody
...
In my pom.xml, I have
Are properties defined in pom.xml available in the execution of an
assembly descriptor invoked from pom.xml via the assembly plugin?
If not, is there a way to pass such definitions to the assembly plugin?
-
To unsubscribe,
Are properties defined in pom.xml available in the execution of an
assembly descriptor invoked from pom.xml via the assembly plugin?
If not, is there a way to pass such definitions to the assembly plugin?
-
To unsubscribe,
I use mvn on the command line. I actually solved the problem by setting the
java version explicitly. I have jdk 1.6.0_33. I found some things on
various sites which suggested mvn always compiles in 1.3 mode. You might
not notice this in an IDE (if it is true) since your IDE is likely to fix
this
On Wed, Nov 28, 2012 at 4:06 PM, Steve Cohen stevec...@comcast.net wrote:
Are properties defined in pom.xml available in the execution of an assembly
descriptor invoked from pom.xml via the assembly plugin?
I don't think so (TBH, I didn't even try, because I first saw… see below)
If not, is
Up until m-c-p 2.5ish the default value for source was 1.3.
That was updated and newer versions of m-c-p use 1.5 as the default
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#source
Maven 3.1.0 will have m-c-p's default version pinned at least at 2.5, so
when that gets
On 11/28/2012 09:27 AM, Thomas Broyer wrote:
On Wed, Nov 28, 2012 at 4:06 PM, Steve Cohen stevec...@comcast.net wrote:
Are properties defined in pom.xml available in the execution of an assembly
descriptor invoked from pom.xml via the assembly plugin?
I don't think so (TBH, I didn't even try,
Good to know that Maven is now only 8 years behind. Better than 12, I
suppose!
Ron
On 28/11/2012 10:40 AM, Stephen Connolly wrote:
Up until m-c-p 2.5ish the default value for source was 1.3.
That was updated and newer versions of m-c-p use 1.5 as the default
Is there a way in maven to echo some text provided via a property in
pom.xml into a text file at a given location?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Steve,
You can use the antrun plugin for that just using ant echo statements.
http://maven.apache.org/plugins/maven-antrun-plugin/
There might be a plugin that can do just the echo, but I don't know what that
would be.
-Jim
-Original Message-
From: Steve Cohen
On Wed, Nov 28, 2012 at 10:13:47AM -0600, Steve Cohen wrote:
Is there a way in maven to echo some text provided via a property in
pom.xml into a text file at a given location?
Perhaps [modest cough] http://mypage.iu.edu/~mwood/FileWeaver/
--
Mark H. Wood, Lead System Programmer
It worked! Thanks a lot. Now trying to figure out how to make the unit test
work...
On Tue, Nov 27, 2012 at 9:23 PM, Barrie Treloar baerr...@gmail.com wrote:
On Wed, Nov 28, 2012 at 9:08 AM, Javier Ortiz javier.ortiz...@gmail.com
wrote:
Added the link to the sources:
On 11/28/2012 10:13 AM, Steve Cohen wrote:
Is there a way in maven to echo some text provided via a property in
pom.xml into a text file at a given location?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
Hi Ron,
Good to know that Maven is now only 8 years behind.
I blame Apple.
-Curtis
On Wed, Nov 28, 2012 at 9:51 AM, Ron Wheeler rwhee...@artifact-software.com
wrote:
Good to know that Maven is now only 8 years behind. Better than 12, I
suppose!
Ron
On 28/11/2012 10:40 AM, Stephen
Use the groovy-maven-plugin:
http://groovy.codehaus.org/GMaven
On Wed, Nov 28, 2012 at 5:13 PM, Steve Cohen sco...@javactivity.org wrote:
Is there a way in maven to echo some text provided via a property in
pom.xml into a text file at a given location?
Now that Oracle are controlling Java on OSX we can no longer blame Apple -
I'd love to see the default become Java 7 now.
And if one needs to lock down to the older versions, lock them down.
On 29/11/2012, at 7:07 AM, Curtis Rueden ctrue...@wisc.edu wrote:
Good to know that Maven is now only
Hi Mark,
Now that Oracle are controlling Java on OSX we can no longer blame
Apple
Well, the new problem is that Java 7 only runs on Lion or later. So then I
blame whoever made that decision. It has forced my projects to stay with
Java 6 (which can for the most part be run in a Java 5
Hi Steve,
Are properties defined in pom.xml available in the execution of an
assembly descriptor invoked from pom.xml via the assembly plugin?
I did a quick test, and it works for me. Anything defined in the pom.xml
properties gets passed to the assembly descriptor, accessible via the
usual
+1
On 28/11/2012 1:36 PM, Mark Derricutt wrote:
Now that Oracle are controlling Java on OSX we can no longer blame Apple -
I'd love to see the default become Java 7 now.
And if one needs to lock down to the older versions, lock them down.
On 29/11/2012, at 7:07 AM, Curtis Rueden
Does not seem to be possible with unpack dependencies.
One option would be to use unpack-dep with the flag that tell to unpack
each dependency in a separate folder and then use the assembly, specifying
the folders in the proper order.
The drawback is that you must list each dependency and
Resource filtering!
On Wednesday, 28 November 2012, Steve Cohen wrote:
Is there a way in maven to echo some text provided via a property in
pom.xml into a text file at a given location?
--**--**-
To unsubscribe, e-mail:
I've not used the Java 1.5 annotations before.
Does anyone know why this might be?
weird as it works for all our plugins :-)
How do you build that ? any sample ?
Got one I can take a look at?
Google isn't helpful because it picks up the javadoc ones too.
2012/11/28 Barrie Treloar baerr...@gmail.com:
I've not used the Java 1.5 annotations before.
Does anyone know why this might be?
weird as it works for all our plugins :-)
How do you build that ? any sample ?
Got one I can take a look at?
On Thu, Nov 29, 2012 at 3:32 AM, Javier Ortiz javier.ortiz...@gmail.com wrote:
It worked! Thanks a lot. Now trying to figure out how to make the unit test
work...
Its more like an integration test than a unit test, as your mojo will
need a lot of structure that it just painful to Mock.
Have a
+1 even though that would trip up lots if users IMHO.
Given that Jdk 6 will be deprecated in spring it might be a good move
Ron Wheeler rwhee...@artifact-software.com wrote:
+1
On 28/11/2012 1:36 PM, Mark Derricutt wrote:
Now that Oracle are controlling Java on OSX we can no longer blame
Hello to all,
i just want to know if someone knows about some influences between
the gwt-maven-plugin and the maven-release-plugin ?
may be someone has already some kind of this experience ?
Thanks in advance.
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 /
i just want to know if someone knows about some influences between
the gwt-maven-plugin and the maven-release-plugin ?
missed to add the link to this:
https://groups.google.com/forum/?fromgroups=#!topic/codehaus-mojo-gwt-maven-plugin-users/dExd-zgzs9k
But doesn't the hint have the
We have used gwt-maven-plugin in combination with the
maven-release-plugin without problems in the Geomajas project. We do not
use compileSourcesArtifacts though, we always either include the sources
in the jars themselves or include the sources jars as dependency in the
project.
Kind
The MavenProject is not a component that is injected by the container. It's
handled by the PluginParameterExpressionEvaluator[1] which looks at all the
non-@component things and sets their values once the Mojo instance is
constructed.
[1]:
Hi Jeff,
I found a solution using the copy-maven-plugin that allows to unpack
and pack (and other operations) :
https://gist.github.com/4164769
The plugin : http://evgeny-goldin.com/wiki/Copy-maven-plugin
Thanks,
Xavier
2012/11/28 Jeff MAURY jeffma...@jeffmaury.com
Does not seem to be
On Thu, Nov 29, 2012 at 8:49 AM, Jason van Zyl ja...@tesla.io wrote:
The MavenProject is not a component that is injected by the container. It's
handled by the PluginParameterExpressionEvaluator[1] which looks at all the
non-@component things and sets their values once the Mojo instance is
see
http://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html
and
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html
2012/11/29 Barrie Treloar baerr...@gmail.com:
On Thu, Nov 29, 2012 at 8:49 AM, Jason van Zyl ja...@tesla.io wrote:
While I would love to assist, this issue has not been consistently
reproducible. It hasn't yet failed on our automated trunk builds, but
consistently fails on our automated branch builds (it consistently fails
for me locally both in the trunk and the branch, but the project's primary
developer
On Thu, Nov 29, 2012 at 9:37 AM, Olivier Lamy ol...@apache.org wrote:
see
http://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html
and
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html
I tried those with his example project I
2012/11/29 Barrie Treloar baerr...@gmail.com:
On Thu, Nov 29, 2012 at 9:37 AM, Olivier Lamy ol...@apache.org wrote:
see
http://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html
and
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html
On Thu, Nov 29, 2012 at 10:14 AM, Olivier Lamy ol...@apache.org wrote:
then don't miss
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-plugin-plugin/artifactId
version3.2/version
configuration
!-- see
Even the stack trace from the NPE would help
On 28 November 2012 23:31, Wheeler, Dennis dwhee...@cobaltgroup.com wrote:
While I would love to assist, this issue has not been consistently
reproducible. It hasn't yet failed on our automated trunk builds, but
consistently fails on our automated
Internally the way @component works is to take the role of component supplied
or figure it out. With that role a lookup against the container is executed.
The MavenProject is not something that is available from the container because
it is not a component. So I doubt it works, unless some magic
magic has been done:
see http://maven.apache.org/plugin-tools/apidocs/src-
html/org/apache/maven/tools/plugin/util/PluginUtils.html#line.40
Le mercredi 28 novembre 2012 18:54:11 Jason van Zyl a écrit :
Internally the way @component works is to take the role of component
supplied or figure it
That's not right, and confusing. It's not a component.
jvz
On 2012-11-28, at 6:57 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
magic has been done:
see http://maven.apache.org/plugin-tools/apidocs/src-
html/org/apache/maven/tools/plugin/util/PluginUtils.html#line.40
Le mercredi 28
I would remove that from the doco. I assume the @Parameter method still works
and just keep that method.
jvz
On 2012-11-28, at 6:57 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
magic has been done:
see http://maven.apache.org/plugin-tools/apidocs/src-
it's confusing for people mastering a lot of things
for normal people, it was really not easy to understand, and not really
documented, neither PluginParameterExpressionEvaluator (which I documented
after I uderstood) nor the '@parameter default-value=${project}
readonly=true' pattern (lots of
Do users often accidentally upgrade major releases of maven without care or
thought?
….maybe I shouldn't ask that tho :)
On 29/11/2012, at 9:47 AM, Manfred Moser manf...@mosabuam.com wrote:
+1 even though that would trip up lots if users IMHO.
no, we choose to do that for ease of use for the average plugin developer
we had a long discussion on how to ease plugin development, find a better name
than expression, understand that such Maven object injection case is best
written as default-value than expression, and so on...
and actual
How does it help by telling them something factually incorrect? A component has
a specific definition of being an instance created by the container.
On Nov 28, 2012, at 7:23 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
no, we choose to do that for ease of use for the average plugin
I wish we had this good discussion in may, when we wroked on plugin-tools ease
of use enhancements
I understand your point
And in fact, when I write that the feature was added partly because parameter
default-value=${project} read-only=true, I see I didn't document it
either, now that I'm able
60 matches
Mail list logo
