date:20120914

Maven Shade Plugin jars, unable to read manifest

2012-09-14 Thread Jeffrey Brekke

I've checked the issues and didn't see this particular problem documented.
When the shade plugin generates a jar comprised of all the classes, the
META-INF/MANIFEST.MF directory and file are lowercased.  The specifications
as I have read them state the case doesn't matter, but along with the lower
case meta-inf/manifest.mf, there is also and upper-case META-INF/ directory
with all the maven pom files in the jar.  I think this situation where
there is a lowercase and uppercaser meta-inf directory is the issue and
causes the manifest.mf file to be unreadable in these jars ( it looks as if
there isn't one ).

Could anyone else confirm this situation, or know if this is a known issue?

-- 
Jeffrey D. Brekke
Wisconsin,  USA

ekke...@gmail.com
jbre...@wi.rr.com
bre...@apache.org

release maven-javadoc-plugin 2.9

2012-09-14 Thread Benson Margulies

I had a party this evening and closed a handful of jiras, some by
fixes, some by invalidity.

Anyone have anything else they want to do before a release?

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Release Maven Changes Plugin version 2.8

2012-09-14 Thread Dennis Lundberg

Hi,
The vote has passed with the following result :

+1 (binding): Hervé Boutemy, Olivier Lamy, Robert Scholte, Dennis Lundberg
+1 (non binding): Tony Chemit

I will promote the artifacts to the central repo.

On 2012-09-11 21:55, Dennis Lundberg wrote:
> Hi,
> 
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=18484
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-053/
> https://repository.apache.org/content/repositories/maven-053/org/apache/maven/plugins/maven-changes-plugin/2.8/maven-changes-plugin-2.8-source-release.zip
> 
> Staging site (wait for the sync):
> http://maven.apache.org/plugins/maven-changes-plugin-2.8/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 


-- 
Dennis Lundberg

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Changes Plugin version 2.8

2012-09-14 Thread Dennis Lundberg

+1 from me

On 2012-09-11 21:55, Dennis Lundberg wrote:
> Hi,
> 
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=18484
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-053/
> https://repository.apache.org/content/repositories/maven-053/org/apache/maven/plugins/maven-changes-plugin/2.8/maven-changes-plugin-2.8-source-release.zip
> 
> Staging site (wait for the sync):
> http://maven.apache.org/plugins/maven-changes-plugin-2.8/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 


-- 
Dennis Lundberg

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

2012-09-14 Thread Baptiste MATHUS

For the record, I just tested a fresh clean install using the svn
repository for git failing tags maven-release-3, 4 & 5: that's almost good
news, they're also failing there.

Cheers

2012/9/13 Baptiste MATHUS 

> Hi,
> Don't know if we need more complete verifications, but here's what I just
> found for the release repo at git://git.apache.org/maven-release.git:
>  Using my current box (m3.0.4 / jdk 1.6.0_33), I wrote a simple 
> script and
> ran it on the maven-release repo.
>
> Summary:
> Only maven-release-3, maven-release-4 & maven-release-5 tags (respectively
> 2.0-beta6, 7 & 8) cannot be built (tests failed). The others build just
> fine.
> Full builds result can be found here:
> https://dl.dropbox.com/u/6790263/result-mrelease-build.log
>
> So that repo seems to be usable. The failing tags above are for quite old
> versions (2007) and I guess nobody will ever want to start patching an beta
> version? If you want, I can also check if svn tags have the same behaviour.
>
> Do you think some more checks should be done? If so, just let me know:
> * building with other JDK versions? other Maven versions?
> * what else?
>
> I think I'll do the same with menforcer repo in the week-end.
>
> Cheers
>
> 2012/9/12 Kristian Rosenvold 
>
>> We still need some verification that the individual repos are ok.
>> (build an old tag,  just look at file trees to see nothing strange
>> happens)
>>
>> You can post that here.
>>
>> Kristian
>>
>> Den 12. s. 2012 kl. 15:55 skrev Olivier Lamy :
>>
>> > 2012/9/12 Baptiste MATHUS :
>> >> I can try and take care of enforcer & release to begin with if no-one
>> >> objects. But I cannot add myself to the wiki even logged in. I guess
>> the
>> >> pages are protected to spammers.
>> > Thanks for the help.
>> > But the task will be "relatively easy" as we have already clones
>> > available for some parts of the svn tree.
>> >
>> > It's just a question of available time from ASF infra folks (normally
>> > already existed volunteers from the project will help too at least I
>> > hope :P )
>> >>
>> >> Cheers
>> >>
>> >> 2012/9/12 Olivier Lamy 
>> >>
>> >>> +1 for keep svn references.
>> >>>
>> >>> FYI I will start migration with moving the following repositories:
>> >>> * surefire
>> >>> * wagon
>> >>> * scm
>> >>>
>> >>> 2012/9/12 Baptiste MATHUS :
>>  2012/9/12 Kristian Rosenvold 
>> 
>> > Are you thinking about the svn references etched into each commit ?
>> >
>> > The current git-svn repos all have this information appended at the
>> > end of each commit:
>> > git-svn-id:
>> >>> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
>> > 13f79535-47bb-0310-9956-ffa450edef68
>> >
>> > Personally I think we should keep them, since they contain the
>> > historical reference to the SVN commit number. And technically we
>> have
>> > a lot
>> > of jiras referencing "r990909" so removing them is not a good idea
>> wrt
>> > traceability of changes.
>> >
>> 
>>  +1000. I was about to answer in the same vein.
>>  I really think that storing as much information of where a gives path
>> >>> comes
>>  from will be very valuable in the future.
>> 
>>  I cannot understand how one could want to get rid of that
>> informations.
>>  Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
>> >>> some
>>  revisions and it's always very useful to be able to find that very
>> >>> revision
>>  in the Git history.
>> 
>>  Cheers
>> 
>>  --
>>  Baptiste  MATHUS - http://batmat.net
>>  Sauvez un arbre,
>>  Mangez un castor !
>>  nbsp;!
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Olivier Lamy
>> >>> Talend: http://coders.talend.com
>> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>
>> >>> -
>> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >>> For additional commands, e-mail: dev-h...@maven.apache.org
>> >>>
>> >>> --
>> >>> Baptiste  MATHUS - http://batmat.net
>> >>> Sauvez un arbre,
>> >>> Mangez un castor !
>> >>> nbsp;!
>> >>> 
>> >>>
>> >
>> >
>> >
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>> --
>> Baptiste  MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> nbsp;!
>>  
>>
>


-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Re: svn commit: r1384747 - in /maven/shared/trunk/maven-shared-utils/src: main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java test/java/org/apache/maven/shared/utils/io/DirectoryS

2012-09-14 Thread Romain Manni-Bucau

SavePoint?
Le 14 sept. 2012 20:04, "Anders Hammar"  a écrit :

> Yes, "Snapshot" is not good. "PointInTime"?
>
> /Anders
> On Fri, Sep 14, 2012 at 3:03 PM, Mark Struberg  wrote:
> > Hi!
> >
> > If anyone has a better name for the 'DirectorySnapshotScanner' I would
> be happy to rename it.
> >
> >
> > What it makes: it takes a snapshot capture of a directory structure and
> compares it with another snapshot capture of that directory to calculate a
> diff (files added/removed)
> >
> > Not sure though if the name 'snapshot' isn't too heavily associated with
> dependency-snapshots, wdyt?
> >
> >
> > We will need this for the incremental build support.
> >
> > LieGrue,
> > strub
> >
> >
> >
> > - Original Message -
> >> From: "strub...@apache.org" 
> >> To: comm...@maven.apache.org
> >> Cc:
> >> Sent: Friday, September 14, 2012 2:57 PM
> >> Subject: svn commit: r1384747 - in
> /maven/shared/trunk/maven-shared-utils/src:
> main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
> test/java/org/apache/maven/shared/utils/io/DirectorySnapshotScannerTest.java
> >>
> >> Author: struberg
> >> Date: Fri Sep 14 12:57:24 2012
> >> New Revision: 1384747
> >>
> >> URL: http://svn.apache.org/viewvc?rev=1384747&view=rev
> >> Log:
> >> MSHARED-243 add DirectorySnapshotScanner
> >>
> >> This allows to take snapshot captures of a directory and
> >> calculate the 'diff' between those (files added/removed).
> >>
> >> Added:
> >>
> >>
> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
> >> (with props)
> >>
> >>
> maven/shared/trunk/maven-shared-utils/src/test/java/org/apache/maven/shared/utils/io/DirectorySnapshotScannerTest.java
> >> (with props)
> >>
> >> Added:
> >>
> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
> >> URL:
> >>
> http://svn.apache.org/viewvc/maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java?rev=1384747&view=auto
> >>
> ==
> >> ---
> >>
> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
> >> (added)
> >> +++
> >>
> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
> >> Fri Sep 14 12:57:24 2012
> >> @@ -0,0 +1,139 @@
> >> +package org.apache.maven.shared.utils.io;
> >> +
> >> +/*
> >> + * Licensed to the Apache Software Foundation (ASF) under one
> >> + * or more contributor license agreements.  See the NOTICE file
> >> + * distributed with this work for additional information
> >> + * regarding copyright ownership.  The ASF licenses this file
> >> + * to you under the Apache License, Version 2.0 (the
> >> + * "License"); you may not use this file except in compliance
> >> + * with the License.  You may obtain a copy of the License at
> >> + *
> >> + *  http://www.apache.org/licenses/LICENSE-2.0
> >> + *
> >> + * Unless required by applicable law or agreed to in writing,
> >> + * software distributed under the License is distributed on an
> >> + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> >> + * KIND, either express or implied.  See the License for the
> >> + * specific language governing permissions and limitations
> >> + * under the License.
> >> + */
> >> +
> >> +import org.apache.maven.shared.utils.CollectionUtils;
> >> +
> >> +import java.io.File;
> >> +import java.util.ArrayList;
> >> +import java.util.List;
> >> +import java.util.Set;
> >> +
> >> +/**
> >> + * Scan for files in a directory at a given time and reports removed
> and added
> >> files
> >> + * between captures.
> >> + */
> >> +public class DirectorySnapshotScanner
> >> +{
> >> +private final static String[] NO_FILES = new String[0];
> >> +
> >> +private File rootDirectory;
> >> +private String[] scannedOldFiles;
> >> +private String[] scannedNewFiles = NO_FILES;
> >> +private String[] filesAdded;
> >> +private String[] filesRemoved;
> >> +
> >> +public DirectorySnapshotScanner( File rootDirectory )
> >> +{
> >> +this.rootDirectory = rootDirectory;
> >> +}
> >> +
> >> +public void capture()
> >> +{
> >> +DirectoryScanner ds = new DirectoryScanner();
> >> +capture( ds );
> >> +}
> >> +
> >> +public void capture( DirectoryScanner ds )
> >> +{
> >> +ds.setBasedir( rootDirectory );
> >> +ds.scan();
> >> +
> >> +scannedNewFiles = ds.getIncludedFiles();
> >> +
> >> +if ( scannedOldFiles != null )
> >> +{
> >> +calculateDiff( scannedOldFiles, scannedNewFiles );
> >> +
> >> +}
> >> +else
> >> +{
> >> +filesAdded = NO_FILES;
> >> +filesRemoved = NO_FILES;
> >> +}
> >> +
> >> +// this attempts new files is the baseline for

Re: svn commit: r1384747 - in /maven/shared/trunk/maven-shared-utils/src: main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java test/java/org/apache/maven/shared/utils/io/DirectoryS

2012-09-14 Thread Anders Hammar

Yes, "Snapshot" is not good. "PointInTime"?

/Anders
On Fri, Sep 14, 2012 at 3:03 PM, Mark Struberg  wrote:
> Hi!
>
> If anyone has a better name for the 'DirectorySnapshotScanner' I would be 
> happy to rename it.
>
>
> What it makes: it takes a snapshot capture of a directory structure and 
> compares it with another snapshot capture of that directory to calculate a 
> diff (files added/removed)
>
> Not sure though if the name 'snapshot' isn't too heavily associated with 
> dependency-snapshots, wdyt?
>
>
> We will need this for the incremental build support.
>
> LieGrue,
> strub
>
>
>
> - Original Message -
>> From: "strub...@apache.org" 
>> To: comm...@maven.apache.org
>> Cc:
>> Sent: Friday, September 14, 2012 2:57 PM
>> Subject: svn commit: r1384747 - in 
>> /maven/shared/trunk/maven-shared-utils/src: 
>> main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java 
>> test/java/org/apache/maven/shared/utils/io/DirectorySnapshotScannerTest.java
>>
>> Author: struberg
>> Date: Fri Sep 14 12:57:24 2012
>> New Revision: 1384747
>>
>> URL: http://svn.apache.org/viewvc?rev=1384747&view=rev
>> Log:
>> MSHARED-243 add DirectorySnapshotScanner
>>
>> This allows to take snapshot captures of a directory and
>> calculate the 'diff' between those (files added/removed).
>>
>> Added:
>>
>> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
>> (with props)
>>
>> maven/shared/trunk/maven-shared-utils/src/test/java/org/apache/maven/shared/utils/io/DirectorySnapshotScannerTest.java
>> (with props)
>>
>> Added:
>> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
>> URL:
>> http://svn.apache.org/viewvc/maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java?rev=1384747&view=auto
>> ==
>> ---
>> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
>> (added)
>> +++
>> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
>> Fri Sep 14 12:57:24 2012
>> @@ -0,0 +1,139 @@
>> +package org.apache.maven.shared.utils.io;
>> +
>> +/*
>> + * Licensed to the Apache Software Foundation (ASF) under one
>> + * or more contributor license agreements.  See the NOTICE file
>> + * distributed with this work for additional information
>> + * regarding copyright ownership.  The ASF licenses this file
>> + * to you under the Apache License, Version 2.0 (the
>> + * "License"); you may not use this file except in compliance
>> + * with the License.  You may obtain a copy of the License at
>> + *
>> + *  http://www.apache.org/licenses/LICENSE-2.0
>> + *
>> + * Unless required by applicable law or agreed to in writing,
>> + * software distributed under the License is distributed on an
>> + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
>> + * KIND, either express or implied.  See the License for the
>> + * specific language governing permissions and limitations
>> + * under the License.
>> + */
>> +
>> +import org.apache.maven.shared.utils.CollectionUtils;
>> +
>> +import java.io.File;
>> +import java.util.ArrayList;
>> +import java.util.List;
>> +import java.util.Set;
>> +
>> +/**
>> + * Scan for files in a directory at a given time and reports removed and 
>> added
>> files
>> + * between captures.
>> + */
>> +public class DirectorySnapshotScanner
>> +{
>> +private final static String[] NO_FILES = new String[0];
>> +
>> +private File rootDirectory;
>> +private String[] scannedOldFiles;
>> +private String[] scannedNewFiles = NO_FILES;
>> +private String[] filesAdded;
>> +private String[] filesRemoved;
>> +
>> +public DirectorySnapshotScanner( File rootDirectory )
>> +{
>> +this.rootDirectory = rootDirectory;
>> +}
>> +
>> +public void capture()
>> +{
>> +DirectoryScanner ds = new DirectoryScanner();
>> +capture( ds );
>> +}
>> +
>> +public void capture( DirectoryScanner ds )
>> +{
>> +ds.setBasedir( rootDirectory );
>> +ds.scan();
>> +
>> +scannedNewFiles = ds.getIncludedFiles();
>> +
>> +if ( scannedOldFiles != null )
>> +{
>> +calculateDiff( scannedOldFiles, scannedNewFiles );
>> +
>> +}
>> +else
>> +{
>> +filesAdded = NO_FILES;
>> +filesRemoved = NO_FILES;
>> +}
>> +
>> +// this attempts new files is the baseline for the next scan
>> +scannedOldFiles = scannedNewFiles;
>> +}
>> +
>> +/**
>> + * @return all files which got scanned during the last capture.
>> + */
>> +public String[] getScannedFiles()
>> +{
>> +return scannedNewFiles;
>> +}
>> +
>> +/**
>> + * @return all files which got d

[ANN] Apache Maven Scm publish Plugin 1.0-beta-1

2012-09-14 Thread Olivier Lamy

Hi,
The Apache Maven Team is pleased to announce the first release of the
SCM Publish Plugin 1.0-beta-1

The maven-scm-publish-plugin is a utility plugin to allow publishing
Maven website to any supported SCM (mostly tested on subversion and
git included gh-pages).
The primary goal was to have an utility plugin to allow Apache
projects to publish Maven websites via the ASF svnpubsub system


  org.apache.maven.plugins
  maven-scm-publish-plugin
  1.0-beta-1


The documentation is available here
http://maven.apache.org/plugins/maven-scm-publish-plugin/

Have Fun!
-- 
The Apache Maven team

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

2012-09-14 Thread Manfred Moser

On Thu, September 13, 2012 7:05 pm, Chris Graham wrote:
> On Thu, Sep 13, 2012 at 2:04 PM, Manfred Moser 
> wrote:
>> I think that the cost is only so high because companies keep waiting
>> until
>> it is too painful. If you constantly keep upgrading a bit here and there
>> and stay up to date with your operating systems, runtime environments,
>> browsers and client site frameworks and so on you would actually be able
>> to save a LOT of money in the long run. But you would have to constantly
>> invest rather than waiting with no investment until things fall apart
>> and
>> then being forced to large costly upgrades.
>>
>>
> When a release has to move through 15 environments before it gets to prod
> (think large government project), and various change control boards etc,
> nothing is easy or cheap.
>
> And that is just for a release of code that we write. Updating the
> underlying technology stack is not a simple or cheap exercise.
>
> It's a matter of scale.
>
> Smaller, more self contained projects may indeed be able to take the
> faster
> route that you suggest.
>
> But it is always a matter of *business* risk, not *developer* led changes.

I understand all that but hear my out for a sec. Why do you think there
are 15 environments and change control board and all that overhead the
first place. Because in the past releases/changes were done every couple
of months or years .. therefore the risk to these changes was VERY high
and that needed to be controlled.

However imho (and many others) it would be less risky to constantly
introduce lots of small changes all the time and roll back these little
changes when necessary. But the software (and product delivered and
therefore the business value to the customer) has to constantly improve
and change and adapt to the needs.

This is only possible if you constantly maintain the software .. and part
of that maintenance is updating architectures, build systems and
everything else. Then each step is small and so is the risk involved.

Now I understand that this is a LARGE change to get there for most
organizations but imho this is where things are happening and how you
deliver the best business value for the LOWEST cost and with the smallest
risks. Just look at how any big place like Amazon or ebay or twitter or
Google or Facebook is doing there infrastructure. It is maintained and
updated and worked on all the time.

And the risk of these changes is smaller than falling behind and
accumulating debt and then having to sort it all out in one big change
that will be much more costly.

>> So it is mostly short sighted management and an absence of real
>> technology
>> leadership in organizations causing this problem imho. And forcing the
>>
>
> I could not disagree with you more. And, in a strange way, you're made the
> very point that I'm trying to get across.
>
> What you've said there is a very developer centric view.
> Which is putting the technology ahead of the business.
> It is the business needs that should be dictating the technology; not the
> other way around.

Not at all. Just read above. I am just putting the long term perspective
of constantly innovating and improving before any short term savings from
a business perspective..

Just my 2c of course ;-)

manfred
> -Chris
>
>
>> pain to stay on old stuff higher (like Oracle is doing with deprecating
>> Java 6 earlier) is actually a good thing.
>>
>> imho Maven 2 should have long been deprecated and removed from the
>> downloads pages..
>>
>> just my 2c though ;-)
>>
>> manfred
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT][VOTE] Apache Maven SCM Publish Plugin beta-1

2012-09-14 Thread Olivier Lamy

Hi,
The vote has passed with the following result:
+1 (binding): Deng Ching, Hervé Boutemy, Olivier Lamy
+1 (non binding): Tony Chemit.

I will finish the release process.

Thanks
-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: svn commit: r1384747 - in /maven/shared/trunk/maven-shared-utils/src: main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java test/java/org/apache/maven/shared/utils/io/DirectoryS

2012-09-14 Thread Mark Struberg

Hi!

If anyone has a better name for the 'DirectorySnapshotScanner' I would be happy 
to rename it.


What it makes: it takes a snapshot capture of a directory structure and 
compares it with another snapshot capture of that directory to calculate a diff 
(files added/removed)

Not sure though if the name 'snapshot' isn't too heavily associated with 
dependency-snapshots, wdyt?


We will need this for the incremental build support.

LieGrue,
strub



- Original Message -
> From: "strub...@apache.org" 
> To: comm...@maven.apache.org
> Cc: 
> Sent: Friday, September 14, 2012 2:57 PM
> Subject: svn commit: r1384747 - in 
> /maven/shared/trunk/maven-shared-utils/src: 
> main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java 
> test/java/org/apache/maven/shared/utils/io/DirectorySnapshotScannerTest.java
> 
> Author: struberg
> Date: Fri Sep 14 12:57:24 2012
> New Revision: 1384747
> 
> URL: http://svn.apache.org/viewvc?rev=1384747&view=rev
> Log:
> MSHARED-243 add DirectorySnapshotScanner
> 
> This allows to take snapshot captures of a directory and
> calculate the 'diff' between those (files added/removed).
> 
> Added:
>     
> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java 
>  
> (with props)
>     
> maven/shared/trunk/maven-shared-utils/src/test/java/org/apache/maven/shared/utils/io/DirectorySnapshotScannerTest.java 
>  
> (with props)
> 
> Added: 
> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
> URL: 
> http://svn.apache.org/viewvc/maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java?rev=1384747&view=auto
> ==
> --- 
> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
>  
> (added)
> +++ 
> maven/shared/trunk/maven-shared-utils/src/main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java
>  
> Fri Sep 14 12:57:24 2012
> @@ -0,0 +1,139 @@
> +package org.apache.maven.shared.utils.io;
> +
> +/*
> + * Licensed to the Apache Software Foundation (ASF) under one
> + * or more contributor license agreements.  See the NOTICE file
> + * distributed with this work for additional information
> + * regarding copyright ownership.  The ASF licenses this file
> + * to you under the Apache License, Version 2.0 (the
> + * "License"); you may not use this file except in compliance
> + * with the License.  You may obtain a copy of the License at
> + *
> + *  http://www.apache.org/licenses/LICENSE-2.0
> + *
> + * Unless required by applicable law or agreed to in writing,
> + * software distributed under the License is distributed on an
> + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> + * KIND, either express or implied.  See the License for the
> + * specific language governing permissions and limitations
> + * under the License.
> + */
> +
> +import org.apache.maven.shared.utils.CollectionUtils;
> +
> +import java.io.File;
> +import java.util.ArrayList;
> +import java.util.List;
> +import java.util.Set;
> +
> +/**
> + * Scan for files in a directory at a given time and reports removed and 
> added 
> files
> + * between captures.
> + */
> +public class DirectorySnapshotScanner
> +{
> +    private final static String[] NO_FILES = new String[0];
> +
> +    private File rootDirectory;
> +    private String[] scannedOldFiles;
> +    private String[] scannedNewFiles = NO_FILES;
> +    private String[] filesAdded;
> +    private String[] filesRemoved;
> +
> +    public DirectorySnapshotScanner( File rootDirectory )
> +    {
> +        this.rootDirectory = rootDirectory;
> +    }
> +
> +    public void capture()
> +    {
> +        DirectoryScanner ds = new DirectoryScanner();
> +        capture( ds );
> +    }
> +
> +    public void capture( DirectoryScanner ds )
> +    {
> +        ds.setBasedir( rootDirectory );
> +        ds.scan();
> +
> +        scannedNewFiles = ds.getIncludedFiles();
> +
> +        if ( scannedOldFiles != null )
> +        {
> +            calculateDiff( scannedOldFiles, scannedNewFiles );
> +
> +        }
> +        else
> +        {
> +            filesAdded = NO_FILES;
> +            filesRemoved = NO_FILES;
> +        }
> +
> +        // this attempts new files is the baseline for the next scan
> +        scannedOldFiles = scannedNewFiles;
> +    }
> +
> +    /**
> +     * @return all files which got scanned during the last capture.
> +     */
> +    public String[] getScannedFiles()
> +    {
> +        return scannedNewFiles;
> +    }
> +
> +    /**
> +     * @return all files which got detected as being added between 2 capture 
> calls
> +     */
> +    public String[] getFilesAdded()
> +    {
> +        return filesAdded;
> +    }
> +
> +    /**
> +     * @return all files which got detected as being removed bet

Re: [VOTE] Release Maven Indexer version 5.0.0

2012-09-14 Thread Vincent Siveton

+1 but same comments.

V.

2012/9/13 Hervé BOUTEMY :
> +1
>
> but there is no site?
>
> Regards,
>
> Hervé
>
> Le mercredi 12 septembre 2012 20:20:24 Tamás Cservenák a écrit :
>> Hi,
>>
>> We solved 6 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112&version=187
>> 22
>>
>> There are still a couple of issues left in JIRA:
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12112&sta
>> tus=1
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-058/
>>
>> Guide to testing staged releases:
>> http://maven.apache.org/guides/development/guide-testing-releases.html
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>>
>>
>> Thanks,
>> ~t~
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Wierd archive deployed?

2012-09-14 Thread Benson Margulies

On Thu, Sep 13, 2012 at 10:15 PM, Chris Graham  wrote:
> :-) [Trying...too...resist...the...urge...to...say...use...eclipse...]

I used to.

Anyway, luckily for us, the newer versions of the toolchain jar do not
upset them, so I updated m-j-p's dependency.


>
> But seriously, a Zip file has "directory" entries in it. They can be a File
> entry, that points to a file's contents, or a Directory entry.
>
> If the (empty) directory entries are not there, then most archive tools
> simply go ahead and create the path and then the file anyway.
>
> Having the Directory entries there is not unique to maven's archiver.
>
> In short, IntelliJ need to fix their code. They should be able to handle
> that situation.
>
> -Chris
>
> On Fri, Sep 14, 2012 at 2:18 AM, Benson Margulies 
> wrote:
>
>> I had trouble working on the javadoc plugin in IntelliJ, and this
>> response came back from their support person.
>>
>> What's special about this artifact? Should I see if making a new
>> release will fix it?
>>
>>
>> Quote starts here:
>>
>> This issue occurs because
>>
>> ...\.m2\repository\org\apache\maven\maven-toolchain\1.0\maven-toolchain-1.0.jar
>> file has some weird archive format that IDEA cannot read:
>> http://dl.dropbox.com/u/2752840/screens/snap2142-1347566987.png .
>>
>> If you look inside this jar with any external unpacker, you'll find
>> that it contains empty file entries that match directories.
>> So it's some Maven packaging issue that affects IDEA ability to
>> properly read this jar.
>>
>> I don't think that we'll want to invest resources into fixing this
>> issue, it should be rather fixed in the Maven repository.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

2012-09-14 Thread Kristian Rosenvold

2012/9/14 Olivier Lamy :
> As far I can see most git beginners use git as they use svn. (hey do
> you remember when you started git and fully break your local clone
> trying to merge some local branches: don't say to me it never happened
> :-) )

I crashed and burned. Badly. Multiple times.

> So our maven tooling must be accessible for the mass (sure extra
> options for geek/nerds is always welcome :-) ) and be operational for
> basic/daily stuff of majority of dev folks.
>>
>> As can be seen from the wiki, I am somewhat at loss for a good
>> branchless solution. I think the best solution is probably to support
>> "trunk only" when running branchless, effectively
>> just move all the checked out dependencies to SNAPSHOT and use trunk
>> for everything. I think we can call it svn mode ;)
> Yup again we must try to build the most generic plugin for most used
> scm (sure better to concentrate efforts on most populars: svn and
> git).

I think it's really ok to default to "trunk" mode (maybe unless you're
checking out a tag of the main project) it's the one feature I
remember very clearly I would've enjoyed the first time I (ever) tried
to change something in maven.

I remember the first time I checked out maven source code quite
clearly, I was checking out repositories like crazy and building just
more and more dependencies until I finally managed to find the one
thing I was interested in. At the time it felt like I had built half
the known universe of components before I reached my goal ;)
(And they all have similar-sounding names; hey; didn't I check out
archiver-archiver just 10 minutes ago ???)

Of course, workspace-plugin would keep the pom changes in the
top-level project as a separate commit, so it doesn't mess up the
actual changeset in the end. (We could support a "patch" command too)

Just my 50 Øre (0.5 Norwegian kroner, recently deprecated).

Kristian

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

2012-09-14 Thread Olivier Lamy

Hi,

2012/9/14 Kristian Rosenvold :
> I updated the docs at
> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
> to include a branch/branchless strategy.
>
> A branch based strategy is real badass if you're comfortable with
> branches. Arguably most git n00bs are not used to a version control
> system with a well functioning branch concept, so a branchless mode of
> operation is required.
Yup that's cool and IMHO could be the default option.
My personnal opinion on that.
As far I can see most git beginners use git as they use svn. (hey do
you remember when you started git and fully break your local clone
trying to merge some local branches: don't say to me it never happened
:-) )
So our maven tooling must be accessible for the mass (sure extra
options for geek/nerds is always welcome :-) ) and be operational for
basic/daily stuff of majority of dev folks.
>
> As can be seen from the wiki, I am somewhat at loss for a good
> branchless solution. I think the best solution is probably to support
> "trunk only" when running branchless, effectively
> just move all the checked out dependencies to SNAPSHOT and use trunk
> for everything. I think we can call it svn mode ;)
Yup again we must try to build the most generic plugin for most used
scm (sure better to concentrate efforts on most populars: svn and
git).

IMHO we have a generic tool for building daily operations which must
not be focused only on the current "à la mode" scm.

And btw some maven projects (I don't want to be focused on tools only
for Apache Maven sources) will continue to use for long dependencies
with some mix of scm.

My 0.02 euros.

>
> Kristian
>
> 2012/9/13 Kristian Rosenvold :
>> IntelliJ would work very happily with just a pom file aggregating pom;
>> which in this case would be just a modules list. The only problem
>> reaIly is that  I have to put it in a subfolder, since "there can be
>> only one" (Highlander).
>>
>> I'm sure we could generate multiple output formats for the aggregating
>> project, does not eclipse have native pom support too ?
>>
>> Kristian  (Only touches eclipse with pitcfork)
>>
>> 2012/9/13 Jason van Zyl :
>>> You may want to look at PSF files in Eclipse if you want to leverage an 
>>> existing format.
>>>
>>> http://wiki.eclipse.org/PSF
>>>
>>> On Sep 13, 2012, at 7:43 AM, Olivier Lamy wrote:
>>>
 Hi,
 This idea looks nice :-).
 I imagine you will retrieve scm locations of dependencies from their poms.
 In such case dependencies can be a mix of scm (git, svn, hg etc..)
 So I would prefer we try to do something more generic to provide such
 features for all scms we support with maven scm (hey we have a very
 generic scm api :-) ).
 Maybe it's the case and just the plugin name confuse me :-).

 2012/9/13 Kristian Rosenvold :
> I have just added wiki document to discuss the design of a totally new
> plugin I have dubbed the "git-workspace-plugin".
>
> The idea is to change the way we work with layered multi-module
> projects in git that will make it a whole lot easier for anyone
> wishing to make a change to do so.
>
> The page is at
> https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
> and I would really appreciate any kind of feedback on this.
>
> Feel free to edit the page, I will also keep it up to date ;)
>
> Kristian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



 --
 Olivier Lamy
 Talend: http://coders.talend.com
 http://twitter.com/olamy | http://linkedin.com/in/olamy

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> --
>>> Jason van Zyl
>>> Founder & CTO, Sonatype
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> -
>>>
>>> Simplex sigillum veri. (Simplicity is the seal of truth.)
>>>
>>>
>>>
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Proposal for new git-workspace-plugin

2012-09-14 Thread Kristian Rosenvold

I updated the docs at
https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
to include a branch/branchless strategy.

A branch based strategy is real badass if you're comfortable with
branches. Arguably most git n00bs are not used to a version control
system with a well functioning branch concept, so a branchless mode of
operation is required.

As can be seen from the wiki, I am somewhat at loss for a good
branchless solution. I think the best solution is probably to support
"trunk only" when running branchless, effectively
just move all the checked out dependencies to SNAPSHOT and use trunk
for everything. I think we can call it svn mode ;)

Kristian

2012/9/13 Kristian Rosenvold :
> IntelliJ would work very happily with just a pom file aggregating pom;
> which in this case would be just a modules list. The only problem
> reaIly is that  I have to put it in a subfolder, since "there can be
> only one" (Highlander).
>
> I'm sure we could generate multiple output formats for the aggregating
> project, does not eclipse have native pom support too ?
>
> Kristian  (Only touches eclipse with pitcfork)
>
> 2012/9/13 Jason van Zyl :
>> You may want to look at PSF files in Eclipse if you want to leverage an 
>> existing format.
>>
>> http://wiki.eclipse.org/PSF
>>
>> On Sep 13, 2012, at 7:43 AM, Olivier Lamy wrote:
>>
>>> Hi,
>>> This idea looks nice :-).
>>> I imagine you will retrieve scm locations of dependencies from their poms.
>>> In such case dependencies can be a mix of scm (git, svn, hg etc..)
>>> So I would prefer we try to do something more generic to provide such
>>> features for all scms we support with maven scm (hey we have a very
>>> generic scm api :-) ).
>>> Maybe it's the case and just the plugin name confuse me :-).
>>>
>>> 2012/9/13 Kristian Rosenvold :
 I have just added wiki document to discuss the design of a totally new
 plugin I have dubbed the "git-workspace-plugin".

 The idea is to change the way we work with layered multi-module
 projects in git that will make it a whole lot easier for anyone
 wishing to make a change to do so.

 The page is at
 https://cwiki.apache.org/confluence/display/MAVEN/git-workspace-plugin
 and I would really appreciate any kind of feedback on this.

 Feel free to edit the page, I will also keep it up to date ;)

 Kristian

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> --
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> -
>>
>> Simplex sigillum veri. (Simplicity is the seal of truth.)
>>
>>
>>
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Maven Shade Plugin jars, unable to read manifest

release maven-javadoc-plugin 2.9

[RESULT] [VOTE] Release Maven Changes Plugin version 2.8

Re: [VOTE] Release Maven Changes Plugin version 2.8

Re: Plan for git migration

Re: svn commit: r1384747 - in /maven/shared/trunk/maven-shared-utils/src: main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java test/java/org/apache/maven/shared/utils/io/DirectoryS

Re: svn commit: r1384747 - in /maven/shared/trunk/maven-shared-utils/src: main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java test/java/org/apache/maven/shared/utils/io/DirectoryS

[ANN] Apache Maven Scm publish Plugin 1.0-beta-1

Re: Release of Maven Indexer 5.0

[RESULT][VOTE] Apache Maven SCM Publish Plugin beta-1

Re: svn commit: r1384747 - in /maven/shared/trunk/maven-shared-utils/src: main/java/org/apache/maven/shared/utils/io/DirectorySnapshotScanner.java test/java/org/apache/maven/shared/utils/io/DirectoryS

Re: [VOTE] Release Maven Indexer version 5.0.0

Re: Wierd archive deployed?

Re: Proposal for new git-workspace-plugin

Re: Proposal for new git-workspace-plugin

Re: Proposal for new git-workspace-plugin

16 matches

Site Navigation

Mail list logo

Footer information