> Therefore I think that
> the in Super-Pom caused some
> trouble and confusion that you might not be aware of.
It should use the version even if you invoke directly from the command
line, if not, that's a separate bug.
-
To uns
+1
On Tue, Jul 28, 2009 at 6:52 PM, Jason van Zyl wrote:
> Hi,
>
> Igor has been submitting patches for over a year now and in the last 12
> weeks he's been submitting some very substantive changes to 3.x.
>
> Igor has done things like create a performance framework for Maven 3.x to
> make sure it
>
> I used the same parent as the jarsigner plugin which does appear to have the
> source archive. I just assumed the -source now contained the self-building
> requirement. Using the same parent and not getting the same output I'll look
> into tomorrow.
That's on me, I haven't finished it yet. My
On Fri, Jul 24, 2009 at 4:36 PM, Joerg Hohwiller 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
> exist.
>
>
Yep, it needs to be closed.
On Sat, Jul 25, 2009 at 7:53 AM, Benjamin
Bentmann wrote:
> Jason van Zyl wrote:
>
>> It's there if you go to the UI, something appears to be wrong with the
>> redirects.
>
> The repo isn't closed, that could explain why it doesn't show up in public
> via the URL.
>
>
>
The maintenance has been completed and the repo never went offline
thanks to Contegix.
On Thu, Jul 23, 2009 at 10:34 PM, Brian Fox 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
> dis
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 additional
What's it waiting for?
2009/7/21 Raphaël Piéroni :
> 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 the release, mea
+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 Porter wrote:
>
> On 21/07/2009, at 1:04 PM, Jason van Zyl wrote:
>
>> On 20-Jul-09, at 8:14 PM, Brett Porter wrote:
>>
>>> Is th
On Tue, Jul 14, 2009 at 9:29 PM, Geoff Clitheroe 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
> http://maven
On Tue, Jul 14, 2009 at 5:33 PM, Geoff Clitheroe wrote:
> Hi Tim,
>
> On Wed, Jul 15, 2009 at 9:23 AM, Tim O'Brien 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, but I
>> did want to let you know tha
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 er
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 Lundberg wrote:
> Hi
>
> For a *single* module project, like one of our Maven plugins, do I
> really have to create an a
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 Gier wrote:
> Daniel Kulp wrote:
>>
>> On Wed July 8 2009 4:13:24 pm Benjamin Bentmann wrote:
>>>
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
Berrigaud wrote:
> Hi Costin,
>
> I assume you
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 Isbell wrote:
> I'm wondering if there are any plans to release the maven-toolchains-plugin
> . It looks like it's still as a 1.0-snapshot. I'
I'm -0 on the 2.0.11 release.
On Tue, Jun 30, 2009 at 11:10 PM, Brett Porter wrote:
>
> On 01/07/2009, at 6:01 AM, Brian Fox wrote:
>
>> On Tue, Jun 30, 2009 at 11:58 AM, Brett Porter wrote:
>>>
>>>
>>> On 01/07/2009, at 1:47 AM, nicolas de loof wrot
On Tue, Jun 30, 2009 at 11:58 AM, Brett Porter 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,
in my approach, I find it just too risky inside an
>>> organization to bring in upgrades without at least one patch release.
>>>
>>> Will anyone yet document justification for upgrading to 2.2/2.1 from
>>> 2.0? JIRA notes are for the "geeks" but a
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 Porter 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 30/06/2009, at 4:12 A
+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
Bentmann wrote:
> John Casey wrote:
>
>> We've solved 28 issues for this release:
>>
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
>
e, start here:
https://docs.sonatype.com/display/NX/OSS+Repository+Hosting
On Sat, Jun 27, 2009 at 2:30 AM, Francis De
Brabandere 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 con
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, Range wrote:
>
> HI Robert,
>
> Many Thanks for the precious information that you have provided. I just got
> a very good starting point
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 Schaible wrote:
> Hi John,
>
> John Casey wrote at Dienstag, 23. Juni 2009
roject-profile has to be located on a very logic 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?
> >
Why not just put those values into the settings.xml?
On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholte 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 bad choice to remove
use new File(basedir,)
On Tue, Jun 23, 2009 at 4:21 PM, Barrie Treloar 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
> Jun 23, 200
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 5:
I say leave it out.
On Tue, Jun 23, 2009 at 10:26 AM, John Casey 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 used by the Hudson
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 Schaible wrote:
> Hi folks,
>
> is there any way to change the transitive behaviour of
borate 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.
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 Schaible wrote:
> Hi John,
>
> John Casey wrote:
>
>> This would be
I have the recording, any particular place I should check it in?
On Wed, Jun 17, 2009 at 4:44 AM, Jason van Zyl 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
> everyone. It's to
the source
release for now. I 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 Jencks wrote:
>
> On Jun 11, 2009, at 4:52 AM, Brian Fox wrote:
>
>
On Thu, Jun 11, 2009 at 4:22 AM, David Jencks 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
>&g
ource bundle processing and how to pull the right pieces together
into the assembly. Otherwise we are pretty close to getting all this
staged and released.
--Brian
On Thu, Jun 4, 2009 at 5:50 PM, Brian Fox wrote:
> Just to bring the thread back up in light of the recent discussions of
> plug
On Wed, Jun 10, 2009 at 8:31 PM, Vincent
Siveton wrote:
> 2009/6/9, nicolas de loof :
>> +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 to add it on Doxia, and I think we need to
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 Hook wrote:
>
> Hi,
>
> I think we now have a correctly s
On Wed, Jun 10, 2009 at 11:31 AM, Kristian Waagan 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
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 Waagan wrote:
> Hello,
>
> Acc
Yes those were just label changes, but i'll update them.
On Sun, Jun 7, 2009 at 4:15 PM, Barrie Treloar wrote:
> On Sun, Jun 7, 2009 at 11:30 PM, Brian Fox wrote:
>> What part doesn't match the screenshots? I updated them last time there were
>> any significant changes.
On Tue, Jun 9, 2009 at 9:25 AM, Vincent Siveton 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 projects than
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 Treloar wrote:
> On Mon, Jun 8, 2009 at 12:10 AM, Br
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 every
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, 200
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 wrote:
> Just don't use their stuff then, clearly they don't want to make it easy
> for users.
>
>
>
s the person who first cut them able to redo them please? (probably
> Brian Fox since his username is in the images)
>
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 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. We don't
>
of the JDK
How would you do that?
>
>
> Nicolas.
>
> 2009/6/5 nicolas de loof
>
> > 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
ase ?
> Arnaud
>
> # Arnaud Héritier
> # http://blog.aheritier.net
>
>
> On Fri, Jun 5, 2009 at 1:48 AM, Barrie Treloar wrote:
>
> > On Fri, Jun 5, 2009 at 7:13 AM, Brian Fox wrote:
> > > On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann <
>
it
was a requirement in the past isn't an option.
On Wed, May 27, 2009 at 12:49 PM, Brian Fox wrote:
>
>
> On Wed, May 27, 2009 at 12:25 PM, John Casey wrote:
>
>>
>>
>> Brian Fox wrote:
>>
>>> On Tue, May 26, 2009 at 10:18 PM, Brett Porter wrote:
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 sev
On Thu, Jun 4, 2009 at 9:44 AM, nicolas de loof wrote:
> Hi,
> just an suggestion for a potential fix to
> http://jira.codehaus.org/browse/MCOMPILER-80
>
> as maven 2.0.9 fixes the plugin version in super POM, we can consider that
> - if maven 2.0.9 + is detected - any version of maven compiler >
2009/5/29 David Jencks
> 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 for
> includes/excl
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.
http://www.sonatype.com/people/2009/05/nexus-indexer-20-incremental
:
>
>> Hi 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
>>>
ere's a terser wya to
> do that, but it's the best I can think of off-hand.) There's nothing
> 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 tw
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 N
On Wed, May 27, 2009 at 12:25 PM, John Casey wrote:
>
>
> Brian Fox wrote:
>
>> On Tue, May 26, 2009 at 10:18 PM, Brett Porter wrote:
>>
>> On 26/05/2009, at 11:11 PM, Brian Fox wrote:
>>>
>>> We're fixing the directoryscanner to allow re
On Tue, May 26, 2009 at 10:18 PM, Brett Porter 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 chai
> 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
Nothing used it but there where some vestigal left overs.
2009/5/24 Brett Porter
> 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,
>> people could a
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 wrote:
>
> On 22-May-09, at 4:36 PM, Jo
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 ne
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 in
+1
On Thu, May 21, 2009 at 10:51 PM, John Casey 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 anyone is actually u
+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
>
>
>
m 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 wrote:
> Brian Fox wrote:
>
>> On Mon, May 18, 2009 at 8:57 AM, Ate Douma wrote:
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 i
On Mon, May 18, 2009 at 8:57 AM, Ate Douma 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. T
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 wrote:
> Check on the list as Br
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 abou
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 wrote:
> There have been a few threads spawned on various ASF lists lately about the
> release process at the ASF and Maven proj
Bump.
On Sun, May 10, 2009 at 9:12 PM, Brian Fox 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 be th
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 wrote:
>
> On May 16, 2009, at 1:48 PM, Joerg Hohwiller wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
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 wrote:
> Is there a more straightforward way to add support for a custo
On Sat, May 16, 2009 at 4:53 PM, Joerg Hohwiller wrote:
> -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 findbugs. In m
>
>
> 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 w
>
>
> 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
On Fri, May 15, 2009 at 4:10 PM, Joerg Hohwiller wrote:
> -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
On Fri, May 15, 2009 at 2:58 PM, Joerg Hohwiller wrote:
> -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 release
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.
O
>
>
> 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
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
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 wrote:
> I don't know when it will be released, but take a look at [1] for how
> to workaroun
There's no source bundle.
On Thu, May 14, 2009 at 3:59 AM, Lukas Theussl wrote:
>
> Hi,
>
> We solved 27 (Doxia) and 3 (Sitetools) issues:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?proj
>
>
>
> 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 struct
>
>
> >
> > 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
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
b
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 P
> > 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 do
On Sat, May 9, 2009 at 5:44 PM, Joerg Hohwiller wrote:
> -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 the complete
On Sat, May 9, 2009 at 4:48 PM, Joerg Hohwiller wrote:
> -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 maven 2.0
On Thu, May 7, 2009 at 4:31 PM, Asgeir S. Nilsen 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:
>
>
> Twingine
> Twingine Public Mirro
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
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 release:perfo
di 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 som
- Ursprüngliche Mail
Von: Brian Fox
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 oth
Yeah, that's what made me think about combining them.
Brett Porter wrote:
On 05/05/2009, at 10:16 AM, Brian Fox wrote:
Why crawl the repo a second time? Tamas has code to generate the
archetype data directly from the index.
True. Is there a way for the indexer to generate it durin
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 en
401 - 500 of 670 matches
Mail list logo
