The previous regressions have been fixed.
Here's the list of issues fixed in 2.0.10:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create
Staged at (self-signed cert for now)
https://repository.zones.apache.org/content/groups/stag
Actually, I found this page: http://docs.codehaus.org/display/MAVEN/Maven+3.0.x
I cannot tell you how happy I am to hear about the rewriting of the artifact
handling. It is the main part of maven that I think has major architectural
issues. I very glad to see that Maven developers have realize
Is there a timeline for a release and there anywhere I can find documentation
on the new features/improvements/changes in said release?
regards,
Jason
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
On Wed, Feb 4, 2009 at 3:39 PM, Wendy Smoak wrote:
> On Wed, Feb 4, 2009 at 4:34 PM, Kalle Korhonen
> wrote:
>
> > The whole point of this thread was to automate it.
>
> How about...
> - write a plugin to modify the text of the file.
> - use the scm plugin to commit the change.
>
>
Yes, consid
On Wed, Feb 4, 2009 at 4:34 PM, Kalle Korhonen
wrote:
> The whole point of this thread was to automate it.
How about...
- write a plugin to modify the text of the file.
- use the scm plugin to commit the change.
--
Wendy
-
On Wed, Feb 4, 2009 at 3:19 PM, Dennis Lundberg wrote:
> Kalle Korhonen wrote:
> > On Wed, Feb 4, 2009 at 2:32 PM, Dennis Lundberg
> wrote:
> >
> >> You should be able to use the available ${project.*} properties in your
> >> index.apt.vm file to add the *current* release. You would still need
Kalle Korhonen wrote:
> On Wed, Feb 4, 2009 at 2:32 PM, Dennis Lundberg wrote:
>
>> You should be able to use the available ${project.*} properties in your
>> index.apt.vm file to add the *current* release. You would still need to
>> manually add the *previous* releases before you start the rele
On Wed, Feb 4, 2009 at 2:32 PM, Dennis Lundberg wrote:
> You should be able to use the available ${project.*} properties in your
> index.apt.vm file to add the *current* release. You would still need to
> manually add the *previous* releases before you start the release
> process though.
Of co
You should be able to use the available ${project.*} properties in your
index.apt.vm file to add the *current* release. You would still need to
manually add the *previous* releases before you start the release
process though.
Kalle Korhonen wrote:
> As part of our release process we create a dist
This can be accomplished with a Doxia snippet macro (
http://maven.apache.org/guides/mini/guide-snippet-macro.html) and a little
bit of creative Ant scripting. Might be too custom of a use case to make it
a plugin.
Kalle
On Tue, Feb 3, 2009 at 11:00 PM, Kalle Korhonen
wrote:
> As part of our re
I have been looking through the archives regarding why, when the source
plugin is attached to the a phase, project builds start producing this
warning.
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
Since it is a warning, I'd like to think that Maven is trying to
Hello Maven list,
I'm trying to use the Webstart plugin to build a jnlp file that has no
main class. This jnlp has mail.jar as a sole resource, and is referred
to by other jnlp files. The reson for this is that Sun sign's mail.jar,
and I can't include it as a resource in the same jnlp that c
I have figured out how to do this using the assembly plugin and have
added the procedure to the JIRA.
---
Todd Thiessen
> -Original Message-
> From: Thiessen, Todd (BVW:9T16)
> Sent: Wednesday, February 04, 2009 1:12 PM
> To: Maven Users List
> Subject: RE: Jar Aggregate javadoc
>
> J
I have a solaris build machine that ftp's the artifacts to a central
location on another computer. It works when using maven 2.0.8. When we
upgraded to maven 2.0.9, it stopped working.
The error that I am getting is:
[11:00:41]: [ERROR] BUILD ERROR
[11:00:41]: [INFO]
---
Could someone explain, or point me to a place that documents, how to
customize the manifest using the Maven2 ear-plugin?
Thanks
Dave
Hi there,
I have three plugins that must be executed on the same phase
(process-classes). How can I set the sequence on each one will be executed?
Thanks in advance!
Thiago Moreira
On Wed, Feb 4, 2009 at 1:46 PM, John Cartwright
wrote:
> Hello All,
>
> could someone suggest a recommendation or best practice for configuring the
> pom.xml to separate the unit and integration tests? I'd like to be able to
> run the unit tests independently of the integration tests.
>
http://d
See this document:
http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Wed, Feb 4, 2009 at 7:46 PM, John Cartwright
wrote:
> Hello All,
>
> could someone suggest a recomm
Hello All,
could someone suggest a recommendation or best practice for configuring
the pom.xml to separate the unit and integration tests? I'd like to be
able to run the unit tests independently of the integration tests.
Thanks!
--john
-
On Wed, Feb 4, 2009 at 8:46 AM, Salgar, Mehmet (external)
wrote:
> Upload process functions but we are not able to see the artifact later
> in the archiva...
Please ask on the Archiva users list. (Archiva is a separate project
and has its own mailing lists.)
You can find subscription info at h
Jira create. Please vote... ;-)
http://jira.codehaus.org/browse/MJAVADOC-225
---
Todd Thiessen
> -Original Message-
> From: Thiessen, Todd (BVW:9T16)
> Sent: Wednesday, February 04, 2009 12:49 PM
> To: Maven Users List
> Subject: RE: Jar Aggregate javadoc
>
> Thanks Nick. I am starti
Thanks Nick. I am starting to look at the assembly plugin to do the
work. I will also look into creating a Jira.
---
Todd Thiessen
> -Original Message-
> From: Nick Stolwijk [mailto:nick.stolw...@gmail.com]
> Sent: Wednesday, February 04, 2009 12:47 PM
> To: Maven Users List
> Subject
Oh my gosh, one of the responders WAS CORRECT!!! The proxy has this
nasty comment all around it!! GOOD JOB TEAM!!! YOU HAD THE ANSWER!!!
Delete that comment and settings works!!!
-Original Message-
From: Antonio Petrelli [mailto:antonio.petre...@gmail.com]
Sent: Wednesday, February 04,
It seems there is no aggregate-jar goal, and I couldn't find any
requests for this in the Jira [1]
Long term solution:
Add a feature request in Jira (and maybe start coding it. ;) )
Short term solution:
Use Maven Assembly Plugin to jar the files in the target/apidocs
Or do both. :)
Hth,
[1] ht
I think this is better asked on the mule mailinglists.
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Wed, Feb 4, 2009 at 6:05 PM, vka wrote:
>
> Hello:
>
> I have 2 versions of an app running on a server, which uses mule to monitor
> a fo
I am looking to "jar" the aggregated javadoc.
Thanks though.
---
Todd Thiessen
> -Original Message-
> From: Antonio Petrelli [mailto:antonio.petre...@gmail.com]
> Sent: Wednesday, February 04, 2009 12:13 PM
> To: Maven Users List
> Subject: Re: Jar Aggregate javadoc
>
> 2009/2/4 Todd
2009/2/4 Todd Thiessen :
> I have benn looking through the archives but can't find out how to
> generate a jar of the aggregate javadoc in a multi-module project. It
> seems this is a limitation.
>
> Is there any way at all to do this?
http://maven.apache.org/plugins/maven-javadoc-plugin/examples/
I have benn looking through the archives but can't find out how to
generate a jar of the aggregate javadoc in a multi-module project. It
seems this is a limitation.
Is there any way at all to do this?
---
Todd Thiessen
-
To unsu
Hello:
I have 2 versions of an app running on a server, which uses mule to monitor
a folder. I would like both of them to run simulataneoulsy they both monitor
different folders. I am trying to create a service for this 2 instances, but
I am running into port issues as both the instance is using
2009/2/4 Horton, Anne B :
> Antonio,
> Thank you for trying to help me. I believe our proxy requires no
> authentication so that would rule out being NTLM -right???
Not necessarily. Do you use Windows and login in a domain? In this
case, most probably the proxy server will follow the authenticatio
Maybe this is a stupid idea, but you didn't forget to uncomment the
proxy settings in the conf.xml file?
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Wed, Feb 4, 2009 at 5:46 PM, Horton, Anne B wrote:
> Antonio,
> Thank you for trying to
Paolo,
I believe this isn't related to your pom setup in the repo, things work fine
with regular java builds, jar packaging, etc it has something to do with
maven's webapp packaging, which isn't following tansitive dependencies. I'll
report back when I've figured out what I'm doing wrong.
Antonio,
Thank you for trying to help me. I believe our proxy requires no
authentication so that would rule out being NTLM -right???
Any other ideas?
Thank you very much in advance,
Anne
-Original Message-
From: Antonio Petrelli [mailto:antonio.petre...@gmail.com]
Sent: Wednesday, Fe
2009/2/4 Horton, Anne B :
> Users,
>
> I just downloaded Maven and tried to run mvn compile. I see it
>
> "Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-p
> lugin/2.2/maven-resources-plugin-2.2 "
>
> And it tries to do this twice.
>
>
>
> It returns "BUILD E
Users,
I just downloaded Maven and tried to run mvn compile. I see it
"Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-p
lugin/2.2/maven-resources-plugin-2.2 "
And it tries to do this twice.
It returns "BUILD ERROR" with
Reason: POM 'org.apache.maven.pl
Taylor Cowan wrote:
I have maven'ized my builds on jena, putting away my long time friend
ant, and as far as jena proper, all is well, however, when I use SDB
like this:
com.hp.hpl.jena
sdb
1.2.0
Maven only brings down jena-2.5.7. I've fixed this by adding a direct
dependency refere
Hi everybody,
we are trying to upload an artifact that is created from the maven
assembly plugin to archiva...(as zip and also jar)
Upload process functions but we are not able to see the artifact later
in the archiva...
Weird thing about it if the same artifact is installed in a local
repositor
The Mojo team is pleased to announce the release of the rpm maven plugin
version 2.0-beta-2.
http://mojo.codehaus.org/rpm-maven-plugin/
To get this update, simply specify the version in your project's plugin
configuration:
org.codehaus.mojo
rpm-maven-plugin
2.0-beta-2
Tha
I use TestNG to do this.
I have my test method to start the server:
*...@beforeclass(groups = {"selenium" })
@Parameters(
{ "selenium-server-address", "browser-type", "application-address" }
)
protected void startSeleniumServer(String seleniumServerAddress,
String b
hi,
how can i run selenese command with more than one browser ? Atm i use
*opera for example. I couldn't find any hint in the
documentation i hope somebody can help me.
Thanks kukudas
--
View this message in context:
http://www.nabble.com/selenium-maven-plugin-howto-specifie-multiple-browsers-
On Wed, Feb 4, 2009 at 6:20 AM, Nick Stolwijk wrote:
> I think you missed the comment about overlay/flatten/shade the dev1
> and dev2 modules.
>
> What are you going to do with the jars of dev1 and dev2?
>
> 1) Use it as dependencies for other maven modules
> In this case you don't need to do anyt
Hi list,
The project I'm working on uses a custom made plugin to download and run
specific versions of artefacts, using their POMs to get their
dependencies.
In-house, this works fine, and for our user on the clients machines
(SunOs 5.9, not that it should matter?), also.
However, a differ
I think you missed the comment about overlay/flatten/shade the dev1
and dev2 modules.
What are you going to do with the jars of dev1 and dev2?
1) Use it as dependencies for other maven modules
In this case you don't need to do anything special, the common modules
will end up as a transitive depen
Wayne Fay wrote:
>
>> The source code must be common, dev1, dev2 etc. are different
>> environments
>> differs only in configuration files.
>
> In that case, I would probably use profiles (which were designed for
> this purpose exactly) and structure the project as follows:
> no dev1, dev2 dir
Geoffrey Wiseman wrote:
>
> parent (pom, multi-module; any common dependencies or dependency
> management,
> plugin management, etc.)
> - common (common source code; jar)
> - dev1 (depends on common; adds config; can overlay/flatten/shade jar if
> you
> like)
> - dev2 (same as dev1, but with it
45 matches
Mail list logo