2010/12/9 fhomasp thomas.peet...@realdolmen.com:
You're talking about Tiles and accessing the parent directory. Could you
explain a bit further?
I have a better idea, here is the source:
http://svn.apache.org/repos/asf/tiles/framework/trunk/assembly/
And the idea of an extra distribution
Sounds like you might be better served by writing your own plugin to do the
filtering, that way you can take the timestamps into consideration.
Also I hope you are putting the filtered java source into a sub-folder of
${basedir}/target
-Stephen
On 8 December 2010 22:49, Marshall Schor
One for each artifact that needs to be released is ok, that wasn't my
question.
I now also have a distributionmodule that takes info from the release
modules in order to group the libraries and to create one release bundle, as
it is explained in the link you don't like much :-)
I'll take a look
I assume you tried the default value for generatedSourcesDirectory?
Haven't used annotation processors myself, my Maven experience just suggests
going with the defaults as much as possible. But if even the defaults don't
work, something is clearly wrong. Either in the plugin or in your config.
:-)
On 07.12.2010 11:29, Stephen Connolly wrote:
On 7 December 2010 10:14, Asmann, Roland roland.asm...@adesso.at wrote:
Hi all,
I was wondering if anybody ever had this problem...
I have a customer who is running a machine with a SUN JDK and one with
an IBM JDK. Now, we've noticed
On 07.12.2010 14:33, Jörg Schaible wrote:
Hi Stephen,
Stephen Connolly wrote:
On 7 December 2010 10:37, Asmann, Roland roland.asm...@adesso.at wrote:
On 07.12.2010 11:29, Stephen Connolly wrote:
On 7 December 2010 10:14, Asmann, Roland roland.asm...@adesso.at
wrote:
Hi
Hi,
lilyevsky wrote:
I am trying to learn how to use annotationProcessor feature with
maven-compiler-plugin 2.3.2 under maven 3.
My configuration is below.
The processor indeed works and it generates the files.
My problem is that the compiler does not see those files during compile
you need to add an exclusion on the dependency that is being brought in by
profile activation.
It was a mistake that profiles include the dependency section as there is
all manor of issues.
The profile gets activated based on the environment where maven is running,
not the environment where the
Hi Roland
Asmann, Roland wrote:
[snip]
If you use toolchains, it should not matter what JRE you use to run
Maven,
the compiler plugin will use the toolchain you specify.
The question you need to ask yourself is which JDK should the
toolchain be
driving, and I cannot answer
Hi!
I'm developing in a war-project. This war project have some plugins. For
different purposes i do need different plugin sets. Of course, it's easy
just to add or remove the plugins as dependency in the POM of the main
project, but I'm supposed to do this in an easier way like a config file so
Hi,
It doesn't work, and there is no option testErrorIgnore... I'm surprised not
to have the same behavior with Maven 2 and Maven 3.
Thanks.
Rémy
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-Sufire-2-6-errors-tp3297429p3298743.html
Sent from the Maven - Users
if they are going to be building your project, they need to install maven,
and such so they will need to have at least some awareness of maven.
But I would instead have a plugin installation mechanism and get the users
to install the plugins into a standard deployed web-app, e.g. how hudson
works
On 09.12.2010 11:29, Stephen Connolly wrote:
you need to add an exclusion on the dependency that is being brought in by
profile activation.
It was a mistake that profiles include the dependency section as there is
all manor of issues.
The profile gets activated based on the environment
On 09/12/2010 7:52 AM, Asmann, Roland wrote:
On 09.12.2010 11:29, Stephen Connolly wrote:
you need to add an exclusion on the dependency that is being brought in by
profile activation.
It was a mistake that profiles include thedependency section as there is
all manor of issues.
The profile
On 09/12/2010 6:15 AM, kdannies wrote:
Hi!
I'm developing in a war-project. This war project have some plugins. For
different purposes i do need different plugin sets. Of course, it's easy
just to add or remove the plugins as dependency in the POM of the main
project, but I'm supposed to do
On 12/9/2010 3:59 AM, Stephen Connolly wrote:
Sounds like you might be better served by writing your own plugin to do the
filtering, that way you can take the timestamps into consideration.
OK, I just thought that since this might be common scenario, there might be an
existing Maven way to do
Bonjour Remy
i reverted all my builds to use surefire 2.4.2
the introduction of Juice IOC injector code for 2.5 and 2.6 caused grief
i dont know if there is a workaround for errors thrown in 2.5 or 2.6
artifacts...i would suggest reverting to 2.4.2
Bon Chance,
Martin
On 9 December 2010 11:10, Rémy remy.tempora...@gmail.com wrote:
Hi,
It doesn't work, and there is no option testErrorIgnore... I'm surprised
not
to have the same behavior with Maven 2 and Maven 3.
FYI... just tried this locally with Maven3 and Surefire 2.5 (and 2.6) and:
I guess I'm going to go with the original approach seeing that I got allmost
everything working. There is only one problem... I'll clarify.
The 2.2 assembly plugin includes the projects artifacts by default in the
dependencySet tag. However there is a tag that *should* resolve this. I've
Start a new thread, I cannot help here.
2010/12/9 fhomasp thomas.peet...@realdolmen.com:
I guess I'm going to go with the original approach seeing that I got allmost
everything working. There is only one problem... I'll clarify.
The 2.2 assembly plugin includes the projects artifacts by
Martin,
Is there an issue for this problem ? surefire 2.7 is about this -- --
close and if there is an issue I can look at it.
Kristian
to., 09.12.2010 kl. 09.09 -0500, skrev Martin Gainty:
Bonjour Remy
i reverted all my builds to use surefire 2.4.2
the introduction of Juice IOC injector
More context on how I got to this phase:
http://maven.40175.n5.nabble.com/Create-complicated-client-jar-release-target-s-td3295582.html
The 2.2 assembly plugin includes the projects artifacts by default in the
dependencySet tag. However there is a tag that *should* resolve this. I've
set it
On 9 December 2010 15:35, Kristian Rosenvold
kristian.rosenv...@gmail.comwrote:
Martin,
Is there an issue for this problem ?
afaik only http://jira.codehaus.org/browse/SUREFIRE-655 which no-one was
able to reproduce
surefire 2.7 is about this -- --
close and if there is an issue I can
I am able to log in via the browser (just using the defaults as we're just
getting started with Nexus, so admin/admin123) to see our repositories.
I've added to local settings:
server
idSnapshots/id
usernameadmin/username
passwordadmin123/password
/server
And
-Original Message-
From: ginni [mailto:gi...@aero.org]
Sent: Thursday, December 09, 2010 8:23 AM
To: users@maven.apache.org
Subject: M2Eclipse deploy to Nexus Repo Failure
I am able to log in via the browser (just using the defaults as we're
just
getting started with Nexus, so
why 2 projects?
it seems 1 maven project with profiles and a batch script will work
something like so:
mvn deploy -P SunProfileName
mvn deploy -P IBMProfileName
On Thu, Dec 9, 2010 at 5:15 AM, Ron Wheeler
rwhee...@artifact-software.comwrote:
On 09/12/2010 7:52 AM, Asmann, Roland wrote:
On
On 09/12/2010 1:08 PM, Jon Paynter wrote:
why 2 projects?
it seems 1 maven project with profiles and a batch script will work
something like so:
mvn deploy -P SunProfileName
mvn deploy -P IBMProfileName
If it works, I would have no objection but 2 projects will work for sure
and everyone knows
good point there.
id opt for the simple solution too.
On Thu, Dec 9, 2010 at 10:18 AM, Ron Wheeler rwhee...@artifact-software.com
wrote:
On 09/12/2010 1:08 PM, Jon Paynter wrote:
why 2 projects?
it seems 1 maven project with profiles and a batch script will work
something like so:
mvn
Can you deploy from the commandline?
I followed the nexus setup instructions from the sonatype site here:
http://www.sonatype.com/books/nexus-book/reference/maven.html
And it worked great the first time.
If it works from the command line, then chanes are its a m2eclipse issue.
On Thu, Dec 9,
Thanks Anders,
I tried the default value and I got one step ahead, not 100% there yet.
First I run the clean build, it generates the source I want under
target/generated-sources-annotations. Still complains about the class not
found when trying to compile the main tree (I use the generated class
I don't like it. 2 Projects means that we have to share code somehow...
Besides, if it was just a simple JAR-file, it would be OK. We have about
7 modules, and I don't really feel like duplicating all of them.
Besides, the only difference we really have is that we trigger Maven
with a
Thanks for responses. Turns out I needed to include my .ssh and passphrase in
addition to the username and password to make it work.
--
View this message in context:
http://maven.40175.n5.nabble.com/M2Eclipse-deploy-to-Nexus-Repo-Failure-tp3299138p3299294.html
Sent from the Maven - Users
Check the source in svn of maven-compiler-plugin.
/Anders (mobile)
Den 9 dec 2010 19.34 skrev lilyevsky leonidilyev...@yahoo.com:
Thanks Anders,
I tried the default value and I got one step ahead, not 100% there yet.
First I run the clean build, it generates the source I want under
On 09/12/2010 1:57 PM, Asmann, Roland wrote:
I don't like it. 2 Projects means that we have to share code somehow...
Besides, if it was just a simple JAR-file, it would be OK. We have about
7 modules, and I don't really feel like duplicating all of them.
You must have heard of libraries? Java
Hi,
Maven is having problems downloading dependencies. Any suggestions?
Here is the command line output
C:\projectmvn -version
Apache Maven 2.0.11 (r909250; 2010-02-11 22:55:50-0700)
Java version: 1.6.0_21
Java home: C:\devtools\Java\jdk1.6.0_21\jre
Default locale: en_US, platform encoding:
According to http://maven.apache.org/plugins/maven-shade-plugin/, the
current version of the stage plugin is 1.4, i.e. 1.4.3 hasn't been released.
On Thu, Dec 9, 2010 at 4:03 PM, Elliot Huntington
elliot.hunting...@gmail.com wrote:
Hi,
Maven is having problems downloading dependencies. Any
Thank you! I don't know how I overlooked that. I thought I checked the
repository and saw it there.
Now, for some reason the plugin is not activated when I run mvn package
I have my pom.xml configured with this:
plugin
groupIdorg.apache.maven.plugins/groupId
Leon, you really have not provided very much information here. I
don't think you need to let them go, but certainly maven _rewards_
following the default or standard approach in most places; in the case
of SVN this would mean that your project root is directly on the
trunk, and the 'trunk' has
I'm using Maven 2.2.1. It won't resolve a dependency with a locked
down version like [1.0.0.6] if the metadata xml file in the local repo
does not have that version. It won't look in my remote repo, which
does have the version I need. But if I delete the metadata xml
file(s) in my local repo,
Ok, some good news. I just did the same test with Maven 3.0.1 and it
worked no problem. It downloaded the new version from the remote repo
like it was supposed to.
But I don't know if I'm ready to migrate to Maven 3.x yet...
Phillip
On Thu, Dec 9, 2010 at 10:00 PM, Phillip Hellewell
Do you have this snippet in the pluginManagement section by any chance? If
so, it does actually bind it.
/Anders
On Thu, Dec 9, 2010 at 23:32, Elliot Huntington elliot.hunting...@gmail.com
wrote:
Thank you! I don't know how I overlooked that. I thought I checked the
repository and saw it
Did you try forcing an update (-U) with Maven 2? I don't know if that
should have worked, but I would have tried it...
/Anders
On Fri, Dec 10, 2010 at 06:19, Phillip Hellewell ssh...@gmail.com wrote:
Ok, some good news. I just did the same test with Maven 3.0.1 and it
worked no problem. It
42 matches
Mail list logo
