's not a trivial matter for a program determine what goes in the
NOTICE file from machine-readable data.
> Hopefully the next one will not take 7 months. I sent the first email out for
> the first 3.1.0 on December 2nd, 2012 :-)
>
> On Jul 13, 2013, at 10:00 AM, sebb wrote:
&
On 13 July 2013 14:54, Jason van Zyl wrote:
> The vote has passed with the following:
>
> +1 Binding: Arnaud, Stephen, Olivier, Hervé
> +1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko
I voted -1 (non-binding) because of the invalid NOTICE file (amongst
other reasons).
>
> I'll
On 12 July 2013 22:12, Robert Scholte wrote:
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&styleName=Html&version=19426
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11530
As the subject says.
This was raised over a year ago and has not even attracted a single comment.
Please could someone look at the issue?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail
On 12 July 2013 22:12, Robert Scholte wrote:
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&styleName=Html&version=19426
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11530
On 12 July 2013 01:39, Chris Graham wrote:
> Hi brian!
>
> I found that only the jakarta-regexp-1.4 jar was in central, so 1.2, 1.3
> and 1.5 (the last) were missing.
> They can be found here: http://archive.apache.org/dist/jakarta/regexp/
>
> I did find bsf-2.4.0, but under the bsf groupId, not w
On 9 July 2013 07:19, Olivier Lamy wrote:
> see the pom:
> http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/pom.xml
Maybe add a comment to the file referring to the POM ?
> plexus-maven-plugin merge the content
> I agree that's not the usual place :-)
>
> 2013/7/9 Chris
On 8 July 2013 10:36, wrote:
> Updated Branches:
> refs/heads/master 7bb5f1957 -> 50a24e541
>
>
> upgrade to rat:0.9 and defensively prepare for maven-parent 24
Warning: RAT 0.9 is a lot slower than 0.8 when scanning large files
that don't have a valid license.
Make sure it does not try to sca
On 8 July 2013 09:26, wrote:
> Author: aheritier
> Date: Mon Jul 8 08:26:19 2013
> New Revision: 1500602
>
> URL: http://svn.apache.org/r1500602
> Log:
> Revert commons-io upgrade. commons-io >= 2.3 requires Java6 or later while we
> are always supporting Java 5
-1
The commit makes two other
Something lke this should do:
svn:mime-type: text/plain; charset=utf-8
Adjust the charset as needed.
On 8 July 2013 07:10, Hervé BOUTEMY wrote:
> good idea: I hate these broken log messages, but as they are only log
> messages, I didn't dig into it
>
> Le lundi 8 juillet 201
On 7 July 2013 23:36, wrote:
> Author: hboutemy
> Date: Sun Jul 7 22:36:42 2013
> New Revision: 1500547
>
> URL: http://svn.apache.org/r1500547
> Log:
> added releases history
>
> Added:
> maven/site/trunk/content/apt/docs/history.apt (with props)
>
> Added: maven/site/trunk/content/apt/do
hat independent reviewers are able to check the
release candidate, should they wish to do so.
>> * We could add a control (enforcer ?) that will compare the content of an
>> archive with an scm tag checkout
>>
>> Arnaud
>>
>>
>> On Sun, Jul 7, 2013 at 9:31 PM
ntent of an
> archive with an scm tag checkout
There is already a Perl tool to compare directory structures:
https://svn.apache.org/repos/private/committers/tools/releases/compare_dirs.pl
I use that, as well as a GUI compare tool.
> Arnaud
>
>
> On Sun, Jul 7, 2013 at 9:31 PM, se
On 7 July 2013 13:45, Chris Graham wrote:
> In this instance, these files are derived files, so does it matter?
I already said that this particular file is probably not an issue.
The issue is that the release process is clearly not infallible.
The assembly plugin does not identify every file it
epancy is found, it can be investigated and fixed.
But the important thing to take from this is that the current release
vote checking process could (and should) be improved.
>
> On 7/6/13 1:35 PM, John Casey wrote:
>>
>> On 7/6/13 11:28 AM, sebb wrote:
>>>
>>&g
The curent release candidate for Apache Maven War plugin 2.4 contains
the following file in the source zip:
maven-archiver/pom.properties
The file is not in SVN or the source jar
As far as I can tell it does not belong in the source zip.
The file is unlikely to do any harm, however the fact that
On 5 July 2013 16:36, Arnaud Héritier wrote:
> On Fri, Jul 5, 2013 at 3:21 PM, sebb wrote:
>
>> On 5 July 2013 12:48, Olivier Lamy wrote:
>> > Hi,
>> > I'd like to release Apache Maven War Plugin 2.4.
>> >
>> > We fixed 10 issue
>> &g
On 5 July 2013 14:46, Stephen Connolly wrote:
> On 5 July 2013 14:43, Stephen Connolly wrote:
>
>> On 5 July 2013 14:32, sebb wrote:
>>
>>> On 5 July 2013 12:48, Olivier Lamy wrote:
>>> > Hi,
>>> > I'd like to release Apache Maven War
On 5 July 2013 14:43, Stephen Connolly wrote:
> On 5 July 2013 14:32, sebb wrote:
>
>> On 5 July 2013 12:48, Olivier Lamy wrote:
>> > Hi,
>> > I'd like to release Apache Maven War Plugin 2.4.
>> >
>> > We fixed 10 issue
>> >
>
On 5 July 2013 14:32, sebb wrote:
> On 5 July 2013 12:48, Olivier Lamy wrote:
>> Hi,
>> I'd like to release Apache Maven War Plugin 2.4.
>>
>> We fixed 10 issue
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18840&styleName=Text&proje
On 5 July 2013 12:48, Olivier Lamy wrote:
> Hi,
> I'd like to release Apache Maven War Plugin 2.4.
>
> We fixed 10 issue
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18840&styleName=Text&projectId=11150
>
> Staging repository:
> https://repository.apache.org/content/repositories/mav
On 5 July 2013 14:27, Olivier Lamy wrote:
> 2013/7/5 sebb :
>> On 5 July 2013 12:48, Olivier Lamy wrote:
>>> Hi,
>>> I'd like to release Apache Maven War Plugin 2.4.
>>>
>>> We fixed 10 issue
>>> http://jira.codehaus.org/secure/Re
On 5 July 2013 12:48, Olivier Lamy wrote:
> Hi,
> I'd like to release Apache Maven War Plugin 2.4.
>
> We fixed 10 issue
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18840&styleName=Text&projectId=11150
>
> Staging repository:
> https://repository.apache.org/content/repositories/mav
On 4 July 2013 23:47, Jason van Zyl wrote:
>
> On Jul 4, 2013, at 6:06 PM, sebb wrote:
>
>> On 4 July 2013 20:35, Stephen Connolly
>> wrote:
>>> I am withdrawing my -1 on the basis of the feedback I have received from
>>> legal-discuss.
>>
>
be neglecting our governance role.
>> >>>
>> >>> If the outcome is that we need to add the license headers to all the
>> test
>> >>> data files, t
On 4 July 2013 14:18, Barrie Treloar wrote:
> On 4 July 2013 22:29, Stephen Connolly
> wrote:
>> I will let Barrie decide on whether we *have to* cancel this vote because
>> of the issues he identified in the NOTICE file.
>
> Sebb noticed it.
>
> I just dig the
On 4 July 2013 12:52, Stephen Connolly wrote:
> On 4 July 2013 12:32, sebb wrote:
>
>> On 4 July 2013 11:05, Stephen Connolly
>> wrote:
>> > I have asked the legal-discuss list for an opinion on test data sets and
>> > license headers. From my reading of
ivileges, not rights,
and come with certain responsibilities.
In particular to ensure that releases are available under the Apache
License, and don't contain any suprises for the end users.
> - Stephen
>
>
> On 1 July 2013 03:56, Barrie Treloar wrote:
>
>> On 1
On 1 July 2013 21:29, wrote:
> Updated Branches:
> refs/heads/master 1a6bc6276 -> b4dc8931f
>
>
> Some updates to start working on a proper LICENCE/NOTICE
>
>
> Project: http://git-wip-us.apache.org/repos/asf/maven/repo
> Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/b4dc8931
> Tr
On 30 June 2013 23:33, sebb wrote:
> On 30 June 2013 19:20, sebb wrote:
>> Reminder: all this thread is just about is adding the following lines
>> to vote e-mails:
>>
>> SVN Tag:
>> https://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-p
On 1 July 2013 07:18, Chris Graham wrote:
> On Mon, Jul 1, 2013 at 4:20 AM, sebb wrote:
>
>> Reminder: all this thread is just about is adding the following lines
>> to vote e-mails:
>>
>> SVN Tag:
>>
>> https://svn.apache.org/repos/asf/maven/plugins/tag
On 1 July 2013 07:18, Chris Graham wrote:
> On Mon, Jul 1, 2013 at 4:20 AM, sebb wrote:
>
>> Reminder: all this thread is just about is adding the following lines
>> to vote e-mails:
>>
>> SVN Tag:
>>
>> https://svn.apache.org/repos/asf/maven/plugins/tag
On 1 July 2013 08:17, Andreas Gudian wrote:
>> 2013/6/26 sebb >:
>> > The mission of the ASF is to release software as source, and to ensure
>> > that the released source is available under the Apache Licence.
>>
>> Excuse me but I have always understand the
On 1 July 2013 03:56, Barrie Treloar wrote:
> On 1 July 2013 06:52, sebb wrote:
>> Another problem: the NOTICE file contains the following spurious text:
>>
>>=
>>== NOTICE file correspo
On 30 June 2013 23:32, Benson Margulies wrote:
> On the one hand, I think that, in many Apache communities, comparing the
> source release to the VCS is the exception and not the rule, and may never
> have happened, even once. (I think that there is at least an even chance
> that some crusty veter
On 30 June 2013 19:20, sebb wrote:
> The mission of the ASF is to release software as source, and to ensure
> that the released source is available under the Apache Licence.
>
> Before a release can be approved it must be voted on by the PMC.
> The review process needs to est
On 30 June 2013 23:28, Stephen Connolly wrote:
> On Sunday, 30 June 2013, sebb wrote:
>
>> On 30 June 2013 21:56, Fred Cooke >
>> wrote:
>> >>
>> >> OK, so what is the Git command to download a copy of the sources that
>> >>
>> >
ors to catch up.
> Robert
>
>
> Op Sun, 30 Jun 2013 22:35:40 +0200 schreef sebb :
>
>> On 30 June 2013 21:25, wrote:
>>>
>>> Author: rfscholte
>>> Date: Sun Jun 30 20:25:21 2013
>>> New Revision: 2333
>>>
>>> Log:
>
"developed by"
- the distinction is important.
Furthermore, the NOTICE file refers to additonal 3rd party software,
but there don't appear to be any LICENSE files for the software.
The licenses should either be in LICENSE.txt or linked therefrom.
-1 (non-binding)
On 30 June 2013 20
On 30 June 2013 21:56, Fred Cooke wrote:
>>
>> OK, so what is the Git command to download a copy of the sources that
>>
> are part of the hash?
>>
>
> git checkout
Does not work for me.
I get the following error message:
fatal: Not a git repository (or any of the parent directories): .git
Thi
On 30 June 2013 21:25, wrote:
> Author: rfscholte
> Date: Sun Jun 30 20:25:21 2013
> New Revision: 2333
>
> Log:
> Store all required release files of every available enforcer version
> Added:
> release/maven/enforcer/
Surely enforcer should be under release/maven/plugins?
Or maybe I have
es in SCM. There's no
way to determine provenance otherwise.
> Fred.
>
> On Sun, Jun 30, 2013 at 8:20 PM, sebb wrote:
>
>> The mission of the ASF is to release software as source, and to ensure
>> that the released source is available under the Apache Licence.
>&g
On 30 June 2013 21:04, Stephen Connolly wrote:
> On Sunday, 30 June 2013, sebb wrote:
>
>> On 29 June 2013 11:47, Robert Scholte >
>> wrote:
>> > Hi Sebb,
>> >
>> > none of these files will end up in Maven Central, they are all used for
>>
On 30 June 2013 20:55, Robert Scholte wrote:
> The Apache Maven team is pleased to announce the release of the Maven
> Enforcer Plugin, version 1.3
>
> The Enforcer plugin provides goals to control certain environmental
> constraints such as Maven version, JDK version and OS family along with many
On 30 June 2013 20:00, Jason van Zyl wrote:
> Here are the release bits for 3.1.0:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-084/
>
> Staged distribution:
>
The mission of the ASF is to release software as source, and to ensure
that the released source is available under the Apache Licence.
Before a release can be approved it must be voted on by the PMC.
The review process needs to establish that the proposed source release
meets those aims.
It's all
On 29 June 2013 11:47, Robert Scholte wrote:
> Hi Sebb,
>
> none of these files will end up in Maven Central, they are all used for
> tests.
However, they do end up in the source release which is published via
the ASF mirrors.
It's vital that all released source files have the a
;>
>> >> Another approach:
>> >> - Always attach the rc-number to the tagname, e.g. maven-foo-2.16rc1,
>> but
>> >> *not* to the version.
>> >> - *After* a successful vote create a copy of tag maven-foo-2.16rc1 as
>> >> maven-foo
The file
http://www.apache.org/dist/maven/KEYS
has two entries for F0E309FF - Vincent Massol
One of them should be deleted.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@ma
On 25 June 2013 12:20, Fred Cooke wrote:
> Absolutely, sebb! This is what I've been saying all along. If I had more
> time I'd vote -1 to every attempted release that used or intended to use
> respun tags/artifacts without revisions and checksums. So here's one for
&g
d to be able to select the
revelant portion of the tree. The tag name is one such way to provide
the information.
> Ralph
>
> On Jun 25, 2013, at 4:14 PM, sebb wrote:
>
>> It would be a lot better to use RC1 RC2 etc initially, and copy the
>> successful tag to the GA ta
On 25 June 2013 21:23, Robert Scholte wrote:
> Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19011
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11530&status=1
>
>
ad of deleting the tag
>> to rename it to e.g. maven-javadoc-plugin-2.9-rc1 using "svn mv".
>>
>> By means of this you are able to easily diff between e.g. released 2.8 and
>> the final 2.9 as well as between 2.9-rc1 and the final 2.9.
>>
>> Regards Mirk
On 26 June 2013 23:54, wrote:
> Author: olamy
> Date: Wed Jun 26 22:54:24 2013
> New Revision: 1497151
>
> URL: http://svn.apache.org/r1497151
> Log:
> add a link to sources to get a bit of peace (I hope at least for few days :-))
-1
wrong URL.
> Modified:
> maven/site/trunk/content/xdoc/d
On 26 June 2013 10:56, Chris Graham wrote:
> On Wed, Jun 26, 2013 at 7:06 PM, sebb wrote:
>
>> I meant: if the pom is created with the correct final URLs in the
>> first place, it won't have to be changed.
>>
>>
> They are. If you'd used the release
On 26 June 2013 02:59, Barrie Treloar wrote:
>>> Then replace
>>> cd target/checkout && mvn clean deploy -Papache-release
>>> with
>>> delete target/checkout
>>> svn co to target/checkout
>>> mvn clean deploy -Papache-release
>>>
>>> Since it was mvn release:perform that created target/checkout i
On 26 June 2013 02:48, Barrie Treloar wrote:
> On 26 June 2013 10:48, sebb wrote:
>> The point is that the ASF release source, and it must be provided for
>> download via the ASF mirrors.
>>
>> See:
>>
>> http://www.apache.org/dev/release.html#host-GA
>&
vé BOUTEMY wrote:
> the jar content isn't updated: so you have jar artifacts inconsistent with svn
>
> Le mercredi 26 juin 2013 01:08:59 sebb a écrit :
>> On 26 June 2013 01:04, Chris Graham wrote:
>> > -1
>> > Except then the poms will point to the wrong place.
&g
On 26 June 2013 02:18, Barrie Treloar wrote:
> On 26 June 2013 10:19, sebb wrote:
>> On 26 June 2013 01:41, Olivier Lamy wrote:
>>> correct.
>>> In case of failure during deploy:
>>> * cd target/checkout && mvn clean deploy -Papache-release
>&
On 26 June 2013 02:14, Barrie Treloar wrote:
> On 26 June 2013 09:47, sebb wrote:
>> I could not find any download links for Maven source packages.
>>
>> As the ASF primary purpose is to release source, and that must be
>> released via the mirror system, there ough
On 26 June 2013 01:41, Olivier Lamy wrote:
> correct.
> In case of failure during deploy:
> * cd target/checkout && mvn clean deploy -Papache-release
> or
> * export/checkout the tag && mvn clean deploy -Papache-release
Neither of those guarantee that the workspace agrees with the tag.
Only by c
On 26 June 2013 01:43, Chris Graham wrote:
> On Wed, Jun 26, 2013 at 10:36 AM, sebb wrote:
>
>> However there is also the possibility that vital files are missing
>> from the source archive.
>> For that to be detected, a comparison with the SVN tag is needed.
>&
On 25 June 2013 20:15, Uwe Schindler wrote:
> Hi,
>
> I agree with sebb. I am not a Maven committer, but the release revision is
> very important in the Lucene Project (where I am the chair).
> We have another workflow, working with revision number:
> - Release manager produces
On 26 June 2013 01:25, Barrie Treloar wrote:
>> And if the "mvn deploy" fails for any reason?
>
> We get this often enough with a crappy connection to our nexus servers.
>
>> Is it necessary to re-run release:perform?
>
> release:perform may be at the stage where it has deleted the
> configuration
On 26 June 2013 01:13, Olivier Lamy wrote:
> For historical reason this has changed etc..
> Use org.apache.maven.plugins (same as groupId)
OK thanks, I'll stick with "plugins" for the new ones then.
>
> 2013/6/26 sebb :
>> Most plugins seem to be sub-packages
I could not find any download links for Maven source packages.
As the ASF primary purpose is to release source, and that must be
released via the mirror system, there ought to be download pages with
links to the source package, sigs, hashes and KEYS file.
Yes, there are source packages for some M
On 26 June 2013 00:34, Chris Graham wrote:
> This appears to be a variant of the "Do we reuse version numbers?"
> discussion of recent times.
> That was resolved.
> Can we please not rehash this?
>
> -Chris
>
>
> On Wed, Jun 26, 2013 at 2:52 AM, sebb wro
On 26 June 2013 01:04, Chris Graham wrote:
> -1
> Except then the poms will point to the wrong place.
Depends how the poms are updated.
>
>
> On Wed, Jun 26, 2013 at 10:01 AM, Gary Gregory wrote:
>
>> On Tue, Jun 25, 2013 at 7:14 PM, sebb wrote:
>>
>> >
Most plugins seem to be sub-packages of org.apache.maven.plugin; just
a few use org.apache.maven.plugins (e.g. enforcer, shade).
Is there a convention as to which to choose, or are the plugins that
use "plugins" an anomaly?
-
To
On 25 June 2013 19:33, Hervé BOUTEMY wrote:
> Le mardi 25 juin 2013 17:52:20 sebb a écrit :
>> And it's not unknown for spurious files to creep into a release
>> (perhaps from a stale workspace - are releases always built from a
>> fresh checkout of the tag?)
> we
her
>>>> than wait until forced to.
>>>>
>>>> On Tue, Jun 25, 2013 at 7:52 PM, Ralph Goers >>> wrote:
>>>>
>>>>> I disagree that the revision is required. I know that the RM is going
>>> to
>>>>> recr
each release candidate. Therefore, so long as I
>>> refetch that tag for every release vote I can be confident that I am
>>> reviewing the release contents.
>>>
>>> Ralph
>>>
>>> On Jun 25, 2013, at 9:52 AM, sebb wrote:
>>>
>>>&g
The mission of the ASF is to release software as source, and to ensure
that the released source is available under the Apache Licence.
Before a release can be approved it must be voted on by the PMC.
The review process needs to establish that the proposed source release
meets those aims.
It's all
On 25 June 2013 11:49, Olivier Lamy wrote:
> 2013/6/25 sebb :
>> I'd like to try deploying a snapshot of the new digest plugin but I
>> get "access denied" errors.
>>
>> Any idea why that should be?
> IMHO you need to be in the maven group.
OK, NP.
I'd like to try deploying a snapshot of the new digest plugin but I
get "access denied" errors.
Any idea why that should be?
I can deploy Common snapshots OK to the same repo; is there an ACL
that only allows Maven committers to deploy snapshots. or is some
other config needed?
-
some expected
differences - e.g. DEPENDENCIES is only in the source archive
> +1 on the release however it is odd that the Release Notes page is empty.
Please fix that on the actual site deploy.
> Ralph
>
> On Jun 24, 2013, at 7:15 PM, sebb wrote:
>
>> On 25 June 2013 02:48, Olivier L
On 25 June 2013 02:48, Olivier Lamy wrote:
> Hi,
> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>
> This version contains the code to fix the javadoc security issue after
> the javadoc generation.
>
> Since previous try I fix the @since for applying the javadoc security fix.
>
> We fixed
On 25 June 2013 00:26, wrote:
> Author: olamy
> Date: Mon Jun 24 23:26:16 2013
> New Revision: 1496295
>
> URL: http://svn.apache.org/r1496295
> Log:
> fix name
>
> Modified:
> maven/plugins/trunk/maven-javadoc-plugin/pom.xml
>
> Modified: maven/plugins/trunk/maven-javadoc-plugin/pom.xml
> UR
On 24 June 2013 23:58, Olivier Lamy wrote:
> 2013/6/25 sebb :
>> On 24 June 2013 13:04, Olivier Lamy wrote:
>>> Hi,
>>> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>>>
>>> This version contains the code to fix the javadoc security
On 24 June 2013 13:04, Olivier Lamy wrote:
> Hi,
> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>
> This version contains the code to fix the javadoc security issue after
> the javadoc generation.
>
> We fixed 6 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&st
On 23 June 2013 01:00, Olivier Lamy wrote:
> 2013/6/23 sebb :
>> Also, is there a Sandbox repo where the plugins can be deployed for testing?
>> Or is it up to users to checkout the source and install the plugins locally?
>
> We can deploy snapshots to repository.a.o
I've just been told about the Maven Sandbox, which seems like it might
be a better location for two general purpose plugins that are
currently being developed at Apache Commons.
Digest
The digest plugin is a simple plugin that can generate hashes
(currently just MD5 and SHA1) for any files specifi
On 21 June 2013 04:00, Steve Goodwin wrote:
> Hi,
>
> I am simply trying to create a .zip from some folders in an svn project.
> When I try to run this a maven build I get the following error:
That's really a question for the Maven Users list.
There are more subscribers to answer your question
https://issues.apache.org/jira/browse/LEGAL-171
On 20 June 2013 15:35, Stuart McCulloch wrote:
> On 20 Jun 2013, at 15:19, sebb wrote:
>
>> On 20 June 2013 14:20, Baptiste MATHUS wrote:
>>> I'm +1 with you on the fact that this code should be included after each
&
d effort here.
> Cheers
>
>
> 2013/6/20 sebb
>
>> On 20 June 2013 13:21, Olivier Lamy wrote:
>> > 2013/6/20 sebb :
>> >> On 20 June 2013 12:15, Olivier Lamy wrote:
>> >>> See https://github.com/olamy/JavadocUpdaterTool
>>
On 20 June 2013 13:21, Olivier Lamy wrote:
> 2013/6/20 sebb :
>> On 20 June 2013 12:15, Olivier Lamy wrote:
>>> See https://github.com/olamy/JavadocUpdaterTool
>>> I added a maven build and a mojo.
>>> IANAL so I don't know if we can integrate the sou
On 20 June 2013 13:08, sebb wrote:
> On 20 June 2013 12:15, Olivier Lamy wrote:
>> See https://github.com/olamy/JavadocUpdaterTool
>> I added a maven build and a mojo.
>> IANAL so I don't know if we can integrate the source of
>> JavadocFixTool.java in javado
javadoc jar has lots of goals that occur in different
phases; the only way to be sure to fix all the issues is to always run
the tool after running Javadoc.
> 2013/6/20 sebb :
>> On 19 June 2013 22:40, Baptiste MATHUS wrote:
>>> Hi,
>>> I think the be
om/AdoptOpenJDK/JavadocUpdaterTool/blob/master/src/main/java/JavadocFixTool.java
That looks exactly like the file that was released by Oracle; anyone
can pick up the tool packaged as a jar from the Oracle web-site.
On it's own, it does not help.
> Cheers
>
>
>
> 2013/6/19 sebb
>
>&
I expect you have all see the news about the Javadoc javascript bug.
It's going to take a long time for everyone to update their Java
installations to Java 1.7 u25. Likewise for builds that need to use
other Java versions, tweaking poms so Java 7 is used for Javadocs
whilst still maintaining compa
On 28 December 2012 01:24, Kristian Rosenvold wrote:
> The Maven team is pleased to announce the release of the Maven
> Surefire Plugin, version 2.13
>
> This release includes the maven-surefire-plugin, which executes the
> unit tests of an application, the maven-surefire-report-plugin, which
> pa
The DIST directory currently contains the following Maven directories:
drwxrwsr-x 7 svnwc svnwc 8 Sep 20 10:59 maven
drwxrwsr-x 4 apbackup maven 5 Sep 1 17:32 maven_pre_svnpubsub
Is the maven_pre_svnpubsub directory still needed?
Is it referenced in any download pages?
--
On 12 February 2012 16:33, Dennis Lundberg wrote:
> The Maven team is pleased to announce the release of the Maven Checkstyle
> Plugin, version 2.9
>
> Generates a report on violations of code style and optionally fails the build
> if violations are detected.
>
> http://maven.apache.org/plugins/
On 17 December 2011 01:46, Stephen Connolly wrote:
> The Maven team is pleased to announce the release of the Maven XXX
> Plugin, version Y.Z
X, Y Z?
> This plugin is used to release a project with Maven, saving a lot of
> repetitive, manual work. Releasing a project is made in two steps:
> prep
Looked around; cannot find out where to report bugs in the apache jar
resource bundle.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
On 28 June 2011 15:40, Benson Margulies wrote:
> Sebb,
>
> I think that you are pointing at the dilemma at the center of this.
>
> Anything like this that we put into the top pom is inherited unless
> overriden, and people are skittish about accidently making everything
&
May I make a plea for the ASF POM to include a link to the
documentation in the comments?
Also, maybe someone can fix the very long comment line starting with:
"As of Version 6, "
The description could be wrapped as well.
On 27 June 2011 21:42, Benson Margulies wrote:
> It occurs to me that th
On 19 June 2011 11:52, Dennis Lundberg wrote:
> On 2011-06-19 00:30, Benson Margulies wrote:
>> I just looked at the 'blocker' issues. We have a variety of very old
>> JIRAs here. None of the ones I looked at have a self-contained test
>> case that would can be downloaded, run, and converted to an
On 6 June 2011 09:23, Dennis Lundberg wrote:
> On 2011-06-05 01:45, sebb wrote:
>> On 4 June 2011 22:02, Dennis Lundberg wrote:
>>> On 2011-06-04 22:44, Benson Margulies wrote:
>>>> Dennis,
>>>>
>>>> Points taken. The web page with dev
Thanks!
On 5 June 2011 17:15, Benson Margulies wrote:
> I've pasted all the checkin comments from my activities this weekend
> into their respective jira.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For add
101 - 200 of 233 matches
Mail list logo
