On Fri, Jul 24, 2009 at 4:36 PM, Joerg Hohwillerjo...@j-hohwiller.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I read the documentation of javadoc-plugin about goal aggregate.
Then I called
mvn javadoc:aggregate and maven failed saying that the goal aggregate does not
The maintenance has been completed and the repo never went offline
thanks to Contegix.
On Thu, Jul 23, 2009 at 10:34 PM, Brian Foxbri...@infinity.nu wrote:
We're scheduling a disk upgrade tonight at midnight pst. During this
time, the repository may be offline while data is moved to larger
We're scheduling a disk upgrade tonight at midnight pst. During this
time, the repository may be offline while data is moved to larger
disks.
Thanks,
Brian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
What's it waiting for?
2009/7/21 Raphaël Piéroni raphaelpier...@gmail.com:
Hello, Benjamin,
Please feel free to suppress those things.
I got in a hurry at work since the attempt to release.
I will retry early september, as i think i will have some spare time.
If anyone has courage to do
+1. The sun repo was the only one that caused me concern (they do
still publish some projects there) but this can be dealt with.
On Mon, Jul 20, 2009 at 11:09 PM, Brett Porterbr...@apache.org wrote:
On 21/07/2009, at 1:04 PM, Jason van Zyl wrote:
On 20-Jul-09, at 8:14 PM, Brett Porter wrote:
On Tue, Jul 14, 2009 at 5:33 PM, Geoff Clitheroeg.clithe...@gmail.com wrote:
Hi Tim,
On Wed, Jul 15, 2009 at 9:23 AM, Tim O'Brientobr...@discursive.com wrote:
FYI, running another mirror is a noble goal, and I'm sure there is a
lot of good that could come of finding innovative ways to index,
On Tue, Jul 14, 2009 at 9:29 PM, Geoff Clitheroeg.clithe...@gmail.com wrote:
Hi Brian,
This is a good idea. Email / subscribe the
repo-maintain...@maven.apache.org list and we can work out the mirror
process there.
Thanks, I will do. FWIW I followed the info a the end of this page
I think jira should remain the consolidated list of bugs fixed during
a release. Having it on the site is important, but specifically I
don't want to have yet another file to update each time i fix a bug.
Grabbing the release notes from jira and updating the site is nice and
efficient and pretty
no...this is what i've been working on just slowly. It's almost done
though, and the idea is that it should just work in almost all cases.
On Thu, Jul 9, 2009 at 4:22 PM, Dennis Lundbergdenn...@apache.org wrote:
Hi
For a *single* module project, like one of our Maven plugins, do I
really have
BTW, we already wrote a proposal on this that got relatively little
feedback:
http://docs.codehaus.org/display/MAVEN/Artifact+resolution+and+repository+discovery
On Wed, Jul 8, 2009 at 5:29 PM, Paul Gierpg...@redhat.com wrote:
Daniel Kulp wrote:
On Wed July 8 2009 4:13:24 pm Benjamin Bentmann
Take a look at the maven-dependency-plugin copy-dependencies code,
this is pretty much exactly what you're trying to do. There are
filters that are in a common jar you can reuse to filter out
transitivity etc.
On Tue, Jul 7, 2009 at 6:21 PM, Samuel Le
Berrigaudsamuel.lb.w...@gmail.com wrote:
Hi
I'm -0 on the 2.0.11 release.
On Tue, Jun 30, 2009 at 11:10 PM, Brett Porterbr...@apache.org wrote:
On 01/07/2009, at 6:01 AM, Brian Fox wrote:
On Tue, Jun 30, 2009 at 11:58 AM, Brett Porterbr...@apache.org wrote:
On 01/07/2009, at 1:47 AM, nicolas de loof wrote:
I'm also fine
I think you were the last to work on it ;-) so you're probably most
qualified to answer that and/or do the release.
On Tue, Jun 30, 2009 at 11:04 PM, Shane Isbellshane.isb...@gmail.com wrote:
I'm wondering if there are any plans to release the maven-toolchains-plugin
. It looks like it's still
, 2009 at 8:05 AM, Jason van Zyljvan...@sonatype.com
wrote:
On 29-Jun-09, at 7:54 PM, Brian Fox wrote:
Yeah get rid of it. Is there really demand for the fixed in 2.0.11? I
feel like it's EOL now.
I would guess the vast majority of users are still using the 2.0.x line
because the 2.1.x
On Tue, Jun 30, 2009 at 11:58 AM, Brett Porterbr...@apache.org wrote:
On 01/07/2009, at 1:47 AM, nicolas de loof wrote:
I'm also fine with this, just would like to avoid some EOL tag on 2.0
that
may be considered as lack of support by some corporate users using (old)
maven releases
Sure,
+1, the issues I had with pre-emptive auth in the last one are fixed.
On Sun, Jun 28, 2009 at 1:01 PM, Benjamin
Bentmannbenjamin.bentm...@udo.edu wrote:
John Casey wrote:
We've solved 28 issues for this release:
Yeah get rid of it. Is there really demand for the fixed in 2.0.11? I
feel like it's EOL now.
On Mon, Jun 29, 2009 at 7:33 PM, Brett Porterbr...@apache.org wrote:
Just a matter of clarity. If its not there, there will be no question about
whether to merge to it or not.
- Brett
On
://docs.sonatype.com/display/NX/OSS+Repository+Hosting
On Sat, Jun 27, 2009 at 2:30 AM, Francis De
Brabanderefranci...@gmail.com wrote:
I just want to release empire-db using nexus. And I thought I had to
be in the maven group to do that but somebody on irc told me it was
not necessary. I contacted Brian Fox
You're above mentioned CI system would then deploy to a repository
manager: http://maven.apache.org/repository-management.html
On Fri, Jun 26, 2009 at 7:23 AM, Rangeranganapei...@yahoo.com wrote:
HI Robert,
Many Thanks for the precious information that you have provided. I just got
a very
Nice. That's an old bug that I saw back in ~2.0.5 but it comes and
goes. This is some core plexus threading issue that isn't specific to
this release. Search jira for that message
On Thu, Jun 25, 2009 at 12:52 AM, Jörg Schaiblejoerg.schai...@gmx.de wrote:
Hi John,
John Casey wrote at
Almost certainly no. The 2.1 you saw mentioned most likely refers to
the old 2.1 that is now 3.0. FWIW, I don't believe this has been or
will be addressed in 3.0.0 which is focused on 2.x compatibility.
http://www.sonatype.com/people/2008/11/a-visual-history-of-maven-2/
On Wed, Jun 24, 2009 at
use new File(basedir,)
On Tue, Jun 23, 2009 at 4:21 PM, Barrie Treloarbaerr...@gmail.com wrote:
Interesting...
[INFO] Executing tasks
[echo] script =
/home/hudson/workspace/plugins-CI-with-maven-2.1.x/jdk/1.5/label/ubuntu/trunk/maven-eclipse-plugin/verify-integration-tests-checks.bsh
Why not just put those values into the settings.xml?
On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholterfscho...@codehaus.org wrote:
I heard some time ago that the profiles.xml were removed in Maven3. Although
I'm still using 2.1.0 I want to be prepared for such changes.
IMHO I think it's a
and
easy to access location, so the best option is next to the pom I guess.
-regards,
Robert Scholte
BRIAN FOX-5 wrote:
Why not just put those values into the settings.xml?
On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholterfscho...@codehaus.org
wrote:
I heard some time ago
The transitivity of a given artifact is controlled by the
artifactHandler, so you would need to introduce a new impl (probably
as an extension) to flip that value to false.
On Tue, Jun 23, 2009 at 7:27 AM, Jörg Schaiblejoerg.schai...@gmx.de wrote:
Hi folks,
is there any way to change the
I say leave it out.
On Tue, Jun 23, 2009 at 10:26 AM, John Caseyjdca...@commonjava.org wrote:
FWIW, the following URL at repository.apache.org includes the staging
repository for wagon:
https://repository.apache.org/content/groups/staging/
I've added this repository location to the group
I'm having trouble getting this version to work against my Nexus
instance. I keep getting authorization errors even though it's setup
for anonymous. Switching back to 2.1.0 works immediately.
On Fri, Jun 19, 2009 at 10:36 AM, Jörg Schaiblejoerg.schai...@gmx.de wrote:
Hi John,
John Casey wrote:
you elaborate on the errors? Do we need to file a JIRA for it?
Brian Fox wrote:
I'm having trouble getting this version to work against my Nexus
instance. I keep getting authorization errors even though it's setup
for anonymous. Switching back to 2.1.0 works immediately.
On Fri, Jun 19, 2009
I have the recording, any particular place I should check it in?
On Wed, Jun 17, 2009 at 4:44 AM, Jason van Zyl jvan...@sonatype.com wrote:
On 17-Jun-09, at 9:02 AM, Brett Porter wrote:
Any chance of rotating it?
No, I don't want to rotate it. Let's just find a time that works for
On Thu, Jun 11, 2009 at 4:22 AM, David Jencksdavid_jen...@yahoo.com wrote:
On Jun 10, 2009, at 6:59 PM, Brian Fox wrote:
Update:
The new assembly plugin and the regex in the source bundle seem to be
working great. I have just one thing to resolve that I had previously
overlooked: The source
haven't built up the motivation to open yet another
open ended discussion to get something agreed upon after the last
fiasco to be honest.
On Thu, Jun 11, 2009 at 12:56 PM, David Jencksdavid_jen...@yahoo.com wrote:
On Jun 11, 2009, at 4:52 AM, Brian Fox wrote:
On Thu, Jun 11, 2009 at 4:22 AM
The auto conversion to m2 artifacts has been stopped, and it's a
manual process now. You should plan to produce M2 artifacts going
forward to get things automatically synced. We can do the conversion
for the existing release.
On Wed, Jun 10, 2009 at 3:22 AM, Kristian Waagankrist...@apache.org
On Wed, Jun 10, 2009 at 11:31 AM, Kristian Waagankrist...@apache.org wrote:
Brian Fox wrote:
The auto conversion to m2 artifacts has been stopped, and it's a
manual process now. You should plan to produce M2 artifacts going
forward to get things automatically synced. We can do the conversion
Ok, we'll cancel the oss.sonatype.org request, unless you still want
us to host the repo for you. I left a comment on the upload request,
we need the artifacts to be signed, everything else looks good.
On Tue, Jun 9, 2009 at 11:15 PM, David Hookd...@bouncycastle.org wrote:
Hi,
I think we now
On Wed, Jun 10, 2009 at 8:31 PM, Vincent
Sivetonvincent.sive...@gmail.com wrote:
2009/6/9, nicolas de loof nicolas.del...@gmail.com:
+1
Could we move the assembly plugin configuration to the plugins parent /
apache-release profile for future plugin releases to conform ASF rules ?
I tried
, Brian Fox bri...@infinity.nu wrote:
On Wed, May 27, 2009 at 12:25 PM, John Casey jdca...@commonjava.org
wrote:
Brian Fox wrote:
On Tue, May 26, 2009 at 10:18 PM, Brett Porter br...@apache.org wrote:
On 26/05/2009, at 11:11 PM, Brian Fox wrote:
We're fixing the directoryscanner to allow
On Tue, Jun 9, 2009 at 9:25 AM, Vincent Sivetonvsive...@apache.org wrote:
Hi folks,
I just spot the r766947 [1] of the ASF pom which add a
pluginManagement tag for all ASF projects.
Some questions:
- some plugins like modello-maven-plugin or plexus-maven-plugin are
more specific for Maven
changes.
On Sun, Jun 7, 2009 at 4:49 AM, Barrie Treloar baerr...@gmail.com wrote:
I've updated http://maven.apache.org/developers/release/releasing.html
but the screen shots need redoing.
Is the person who first cut them able to redo them please? (probably
Brian Fox since his username
I would drop the version from the docs if you're concerned of it being
out of date. I don't think we should worry about updating that page
continuously if we change a version in the pom.
On Sun, Jun 7, 2009 at 4:17 PM, Barrie Treloarbaerr...@gmail.com wrote:
On Mon, Jun 8, 2009 at 12:10 AM,
Just don't use their stuff then, clearly they don't want to make it easy for
users.
On Sun, Jun 7, 2009 at 5:19 AM, Tim Pizey t...@paneris.org wrote:
Hi Carlos,
I passed what you said on to the Bouncy Castle guys, but they said:
It's pretty simple. We publish to our website. That's it.
.
Is the person who first cut them able to redo them please? (probably
Brian Fox since his username is in the images)
If someone is interested in maintaining the poms and tracking their
releases, we can set up a repository at oss.sonatype.org.
On Sun, Jun 7, 2009 at 6:57 AM, Brian Fox bri...@infinity.nu wrote:
Just don't use their stuff then, clearly they don't want to make it easy
for users.
On Sun, Jun 7
ok create a new project issue here:
https://issues.sonatype.org/browse/OSSRH and those interested in maintaining
it can add a comment to the issue to get privs.
On Sun, Jun 7, 2009 at 7:30 AM, Robert Burrell Donkin
robertburrelldon...@gmail.com wrote:
On Sun, Jun 7, 2009 at 3:18 PM, Brian
The version in the pom is the locked down version for our plugins to use.
The latest release plugin is 2.0-beta-9:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/
You can override that version in your pom if you are releasing a plugin...we
don't update the parent
would you do that?
Nicolas.
2009/6/5 nicolas de loof nicolas.del...@gmail.com
Right, so do we agree to upgrade default-value to 1.5 in a new 2.1 branch
of the compiler plugin (with required warnings in release note) ?
2009/6/5 Olivier Lamy ol...@apache.org
2009/6/4 Brian Fox bri
On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Arnaud HERITIER wrote:
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't help our users to have them
waiting
all our releases for several
in the past isn't an option.
On Wed, May 27, 2009 at 12:49 PM, Brian Fox bri...@infinity.nu wrote:
On Wed, May 27, 2009 at 12:25 PM, John Casey jdca...@commonjava.orgwrote:
Brian Fox wrote:
On Tue, May 26, 2009 at 10:18 PM, Brett Porter br...@apache.org wrote:
On 26/05/2009, at 11:11 PM
# Arnaud Héritier
# http://blog.aheritier.net
On Fri, Jun 5, 2009 at 1:48 AM, Barrie Treloar baerr...@gmail.com wrote:
On Fri, Jun 5, 2009 at 7:13 AM, Brian Fox bri...@infinity.nu wrote:
On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Arnaud
2009/5/29 David Jencks david_jen...@yahoo.com
I'm eager to see this get out... this version works fine for me after I
hacked the assembly descriptor parents so I could build it (no idea why I
couldn't get to the parent snapshots)
I'm not convinced all the worrying about regular expressions
Your best bet is to use the nexus-indexer api jar to access the data. This
will keep you from having to deal with the contents, which in the old .zip
are a lucene format but in the new .gz incrementals is a special binary
format.
Brian,
That would be fantastic!
Cheers,
Daniel
Brian Fox a �crit :
We can try a release maybe next week. We first have to get some assembly
and
parent pom things fixed to get our releases back in compliance with asf
policy.
On Thu, May 14, 2009 at 8:42 AM, Nick Stolwijk
On Tue, May 26, 2009 at 10:18 PM, Brett Porter br...@apache.org wrote:
On 26/05/2009, at 11:11 PM, Brian Fox wrote:
We're fixing the directoryscanner to allow regular expressions in addition
to the ant syntax.
Cool, but that's another release in the chain, right?
It's already to go
On Wed, May 27, 2009 at 12:25 PM, John Casey jdca...@commonjava.org wrote:
Brian Fox wrote:
On Tue, May 26, 2009 at 10:18 PM, Brett Porter br...@apache.org wrote:
On 26/05/2009, at 11:11 PM, Brian Fox wrote:
We're fixing the directoryscanner to allow regular expressions in
addition
The problem with this is two-fold actually,
The url representation currently doesn't encapsulate the other parts of the
dependency declaration like optional or scope. Further, it is difficult to
deterministically reverse a url like that back to the GAV components... we
struggle with this often in
ambiguous there, is there? It's also extensible.
cheers,
Christian.
On 27-May-09, at 22:24 , Brian Fox wrote:
The problem with this is two-fold actually,
The url representation currently doesn't encapsulate the other parts of
the
dependency declaration like optional or scope. Further
their non-build
target directories.
- Brett
On 21/05/2009, at 7:14 AM, Brian Fox wrote:
Introducing the configurability in the descriptor itself requires more
changes to the assembly code than I think we should tackle right now. I
also
think we should strive to build a descriptor
Nothing used it but there where some vestigal left overs.
2009/5/24 Brett Porter br...@apache.org
Wasn't it already deprecated in a previous release of 2.0.x anyway?
On 22/05/2009, at 12:51 PM, John Casey wrote:
Sounds good to me. If we remove it from the default lifecycle mapping,
+1
On Thu, May 21, 2009 at 10:51 PM, John Casey jdca...@commonjava.org wrote:
Sounds good to me. If we remove it from the default lifecycle mapping,
people could always add it back in...at least then they'd definitely know if
they need it. :-)
Having said that, I'd be *very* surprised if
I don't think we should take away the ability of a user to override a phase
in a plugin. For things like the dependency plugin, I specify a sensible
default, but there are many valid cases to run that plugin in other phases,
I do it myself.
I tend to think the current functionality is working as
On Fri, May 22, 2009 at 4:23 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Jason van Zyl schrieb:
We could even do something like @phase package,install if you truly think
something belongs and has been tested to run in those phases.
Nice idea, but maybe a dedicated new
I feel like this is pretty low on the list of problems to be solved, but if
the allowed phases can be a wildcard, then I guess I'm neutral on the idea.
I think things like pom versioning are far more pressing.
On Fri, May 22, 2009 at 8:10 PM, Jason van Zyl jvan...@sonatype.com wrote:
On
+1
On Thu, May 21, 2009 at 8:09 AM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Paul Gier wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-028/
Staging site:
http://maven.apache.org/ant-tasks-2.0.10/
+1
Benjamin
the assembly, but several projects in maven
use target folders in their test resources (archetype, install, deploy). The
solution to this yet is still undefined.
On Mon, May 18, 2009 at 11:36 AM, Ate Douma a...@douma.nu wrote:
Brian Fox wrote:
On Mon, May 18, 2009 at 8:57 AM, Ate Douma a...@douma.nu
That was the bug i mentioned that needs to be fixed first ;-)
The excludes will only work for the current project, not all child projects
if they weren't already clean. Since my intents is to insert this into the
release profile, I should be able to make it work pretty reliably. I'm
concerned
My understanding of the requirements for the source release are that they
should match identically to the source used to build the binaries. For all
intents and purposes, they should have the same content as the tag.
On Mon, May 18, 2009 at 10:06 AM, Jason van Zyl jvan...@sonatype.comwrote:
On Mon, May 18, 2009 at 8:57 AM, Ate Douma a...@douma.nu wrote:
Brian Fox wrote:
It's been a little slow going, but here's an update of where I'm at:
I branched assembly 2.2-beta-4-SNAPSHOT[1] from the 2.2-beta-3 tag and
renamed the trunk to 2.2-beta-5. The runOnlyOnExecutionRoot flag has
The most important thing is that it has the lowest version possible, which
seems to be the case in the second proposal. When it gets deployed, the
metadata would be updated, but Nexus could correct this back to the right
version pretty easily. (you'd have to do it by hand w/o nexus).
Otherwise if
Bump.
On Sun, May 10, 2009 at 9:12 PM, Brian Fox bri...@infinity.nu wrote:
It's time to start looking at the problems with the current 2.x resolution
scheme as it specifically relates to repository declaration and discovery.
I've created the start of a document at [1]. This should
/plugins/branches/maven-assembly-plugin-2.2-beta-4
[2]
https://svn.apache.org/repos/asf/maven/resources/trunk/apache-source-release-assembly-descriptor
On Mon, May 4, 2009 at 9:01 PM, Brian Fox bri...@infinity.nu wrote:
There have been a few threads spawned on various ASF lists lately about
On Sat, May 16, 2009 at 4:53 PM, Joerg Hohwiller jo...@j-hohwiller.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
E.g. with maven 2.0.x you could have a module included in your
toplevel pom that you also add as dependency to some plugin such
as checkstyle or
You could probably also add it to a jar and add that as a dependency in the
plugin block of your pom. The archiver looks up the unarchiver impl and it
needs to be known to plexus.
On Sat, May 16, 2009 at 7:20 PM, Tim O'Brien tobr...@discursive.com wrote:
Is there a more straightforward way to
Also be aware that 2.1/2.2 already do some pom transformations, so this
would have to extend instead of replicate what's already there.
On Sat, May 16, 2009 at 5:14 PM, Ralph Goers ralph.go...@dslextreme.comwrote:
On May 16, 2009, at 1:48 PM, Joerg Hohwiller wrote:
-BEGIN PGP SIGNED
I don't think we should go out of our way yet to convert everything to
java5, preserving 1.4 compatibility (essentially 2.0/2.1 compatibility)
should be considered. However if there's a reason, like the checkstyle
update requies java 5, then we should do it and set a prerequisite of maven
2.2.0.
On Fri, May 15, 2009 at 2:58 PM, Joerg Hohwiller jo...@j-hohwiller.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
By inheriting the version, groupId, etc. from the parent - yes. The
release plugin still handles the pom transformations and the tagging
(SCM URLs, snapshot to
On Fri, May 15, 2009 at 4:10 PM, Joerg Hohwiller jo...@j-hohwiller.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I think you are referring to one of the other patches that was
submitted, not what I committed to the MNG-624 branch.
MNG-624 or maven-2.1.x-MNG-624 ?
A
Do you need simple IT-projects that I shall attach to MNG-4161 and related?
Sample ITs for sure, and some level of detail in a proposal like these:
http://docs.codehaus.org/display/MAVENUSER/User+Proposals
You have to understand that although the problem might seem trivial, fixes
for problems like this can't break existing builds. That makes even the
simplest fix challenging.
Not only that, it needs to cooperate with other functionality... just like
we found with the previous patch. It would
There's no source bundle.
On Thu, May 14, 2009 at 3:59 AM, Lukas Theussl ltheu...@apache.org wrote:
Hi,
We solved 27 (Doxia) and 3 (Sitetools) issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleName=Htmlversion=15073
We can try a release maybe next week. We first have to get some assembly and
parent pom things fixed to get our releases back in compliance with asf
policy.
On Thu, May 14, 2009 at 8:42 AM, Nick Stolwijk nick.stolw...@gmail.comwrote:
I don't know when it will be released, but take a look at [1]
I was blocked by some IT issues in the assembly plugin. I broke through that
last night, so I can finish up the ITs. David Jenks found another issue with
2.2-beta-3 that causes the source jars to be packaged with absolute paths. I
will need to fix this as well before we can use it globally. If you
OK. So you would NOT mind if maven adds some new features that
are compatible to older versions of maven.
Thats all I am fighting for.
No fighting required, just make a patch. If it's truly backwards compatible,
then there wouldn't be much reason for it to be declined.
I'm interested in
Can you give more details about what doesn't work or doesn't match your
process?
E.g. it tried to convince me to release all modules of my entire project
and complained if some module had a non SNAPSHOT version.
Since it's going to convert a module to a release version, you shouldn't
As I already said, I talked about release-plugin and my view of the world
and it seems NOT to fit together. My POM-tree follows strict logical
aspects that is motivated by the architecture of the project and NOT by
the philosophy of some plugin.
I'm trying to understand your structure and
Are you using the release plugin?
Nope! I tried it and came to the point that is no good for me.
I also had a discussion with the developers long time ago
and filed some feature request. Anyhow I still think this
is the wrong approach for me.
Can you give more details about what doesn't
I agree that this (lack of generics) can be a problem, but concur that it's
not the most pressing thing, particularly with 3.x looming ahead. Fixing
bugs in 2.x would serve the users far more and once 3.x stabilizes, then we
can add generics if they aren't there yet.
On Sun, May 10, 2009 at 3:48
It's time to start looking at the problems with the current 2.x resolution
scheme as it specifically relates to repository declaration and discovery.
I've created the start of a document at [1]. This should be the place to
gather feedback and use cases that will help drive towards a more complete
On Sat, May 9, 2009 at 4:48 PM, Joerg Hohwiller jo...@j-hohwiller.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I found that there is a little list of incompatibilities form m2.1 at:
http://maven.apache.org/release-notes.html
However there are a lot more.
E.g. with
On Sat, May 9, 2009 at 5:44 PM, Joerg Hohwiller jo...@j-hohwiller.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
absolutely everybody having large maven projects is
annoyed by maintaining the versions in all the poms.
Are you using the release plugin?
Additionally
Oleg Gusakov wrote:
fyi:
- maven password encryption uses SHA-256 and switching to SHA-512
could be done using optional encrypted string attributes to ensure
decryption of the existing passwords. SHA-256 is already SHA2 family
and has not been cracked yet, so we can wait. Main question was
On Thu, May 7, 2009 at 4:31 PM, Asgeir S. Nilsen asge...@gmail.com wrote:
I've set up a local Nexus repository mirroring some central
repositories. I'm using Maven 2.1.0.
In settings.xml I've set up the mirror as such, using the new mirrorOf
syntax:
mirror
idTwingine/id
: Brian Fox bri...@infinity.nu
An: dev@maven.apache.org
Gesendet: Dienstag, den 5. Mai 2009, 03:01:25 Uhr
Betreff: Update on ASF Release requirements
There have been a few threads spawned on various ASF lists lately about the
release process at the ASF and Maven projects and other Apache projects
05 mai 2009 00:12:55, Brian Fox a écrit :
Why would you have a symlink in your target folder to someplace
important?
Here is a quick example that came to my mind : Imagine you package a
tarball
containing such a symlink and that during the build you have to extract it
to
change
What options are being passed to the release invocation? It's using -f
which seems to be invalid.
Paul MERLIN wrote:
Hey,
I had no issue building my projects.
release:prepare is working but release:perform is not (see the trace below).
I switched to 2.1.0 right after that and the
Changes like this are pretty disastrous:
-private MapString, ArtifactVersion managedVersionMap;
+private MapString, Artifact managedVersionMap;
Does it even compile?
John Casey wrote:
Can you please take a look at any other code you might have
automatically fixed using Eclipse's
Maybe that code could be rolled into the indexer since it's the source
of the data.
Tamás Cservenák wrote:
We could create a CLI tool out of Nexus Archetype Plugin in similar manner
as Nexus Indexer CLI exists (or even make those two CLIs
one?) Naturally, the Archetype CLI would required
Why would you have a symlink in your target folder to someplace important?
On Mon, May 4, 2009 at 5:25 PM, Bouiaw bou...@gmail.com wrote:
Hi,
Sorry to write again about clean plugin, but there is currently 2 VERY big
bugs in Maven clean with no workaround.
Just so it's clear, I'm -1 on this commit. I see things like:
-private MapString, ArtifactVersion managedVersionMap;
+private MapString, Artifact managedVersionMap;
And that means it wasn't done properly and thus I have no faith in the rest
of the commit. Please revert this.
On Mon, May
.
There's no need to introduce additional risk for nearly no gain.
On Fri, May 1, 2009 at 11:05 AM, Brian Fox bri...@infinity.nu wrote:
I'm not sure if this is in scope of what John is trying to do wrt to 2.2.
Jason van Zyl wrote:
I don't believe anyone actually agreed to this yet. Are you sure
Why crawl the repo a second time? Tamas has code to generate the
archetype data directly from the index.
Brett Porter wrote:
Don't we already have the archetype:crawl mojo?
On 05/05/2009, at 3:52 AM, Brian Fox wrote:
Maybe that code could be rolled into the indexer since it's the
source
There have been a few threads spawned on various ASF lists lately about
the release process at the ASF and Maven projects and other Apache
projects that use Maven being compliant.
A documentation patch for the release page at
http://www.apache.org/dev/release.html is pending, but it's close
401 - 500 of 663 matches
Mail list logo
