On Oct 24, 2009, at 2:25 PM, Sean Owen wrote:
Just to coordinate our efforts --
I tried forcing DNS resolution of svn.apache.org to US servers. Same
results. I eventually reach this error:
svn: Path 'https://svn.apache.org/repos/asf/lucene/mahout/tags/
mahout-0.2'
does not exist in revision 829426
and no amount of svn update or repeating release:prepare does the
trick.
Grant, am I right in thinking you are getting past this part? if so,
I'd judge it more important to figure out how you can move ahead so we
can finally get a release out of this. (And then return to figuring
out why it doesn't work here.)
Looks like it is a question of enabling this
<tarLongFileMode>gnu</tarLongFileMode> in the release profile. One
thing I don't see is where this whole release profile is defined --
assume it's external, but where?
This is in the top level pom.xml under the <profile> section. It is
already defined there.
As an aside, what in the process is creating a 2+GB tar file??
On Sat, Oct 24, 2009 at 12:08 PM, Grant Ingersoll
<[email protected]> wrote:
It looks like it is picking it up:
Configuring mojo
'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:single'
-->
[INFO] [DEBUG] (s) appendAssemblyId = true
[INFO] [DEBUG] (f) attach = true
[INFO] [DEBUG] (s) basedir = .../projects/lucene/mahout/mahout-
clean
[INFO] [DEBUG] (s) descriptorRefs = [Ljava.lang.String;@1cf7cbd1
[INFO] [DEBUG] (f) dryRun = false
[INFO] [DEBUG] (s) finalName = mahout-0.2
[INFO] [DEBUG] (f) ignoreDirFormatExtensions = false
[INFO] [DEBUG] (s) ignoreMissingDescriptor = false
[INFO] [DEBUG] (s) includeSite = false
[INFO] [DEBUG] (s) localRepository = [local] ->
file:///Volumes/User/grantingersoll/.m2/repository
[INFO] [DEBUG] (s) outputDirectory =
.../projects/lucene/mahout/mahout-clean/target
[INFO] [DEBUG] (f) project = MavenProject:
org.apache.mahout:mahout:0.2 @
.../projects/lucene/mahout/mahout-clean/pom.xml
[INFO] [DEBUG] (s) reactorProjects = [MavenProject:
org.apache.mahout:mahout:0.2 @
.../projects/lucene/mahout/mahout-clean/pom.xml, MavenProject:
org.apache.mahout:mahout-parent:0.2 @
.../projects/lucene/mahout/mahout-clean/maven/pom.xml, MavenProject:
org.apache.mahout:mahout-core:0.2 @
.../projects/lucene/mahout/mahout-clean/core/pom.xml, MavenProject:
org.apache.mahout:mahout-taste-webapp:0.2 @
.../projects/lucene/mahout/mahout-clean/taste-web/pom.xml,
MavenProject:
org.apache.mahout:mahout-utils:0.2 @
.../projects/lucene/mahout/mahout-clean/utils/pom.xml, MavenProject:
org.apache.mahout:mahout-examples:0.2 @
.../projects/lucene/mahout/mahout-clean/examples/pom.xml]
[INFO] [DEBUG] (f) remoteRepositories = [[codehausSnapshots] ->
http://snapshots.maven.codehaus.org/maven2, [apacheSnapshots] ->
http://people.apache.org/maven-snapshot-repository/,
[apache.snapshots] ->
http://repository.apache.org/snapshots, [central] ->
http://repo1.maven.org/maven2]
[INFO] [DEBUG] (s) siteDirectory =
.../projects/lucene/mahout/mahout-clean/target/site
[INFO] [DEBUG] (f) skipAssembly = false
[INFO] [DEBUG] (s) tarLongFileMode = gnu
[INFO] [DEBUG] (s) tempRoot =
.../projects/lucene/mahout/mahout-clean/target/archive-tmp
[INFO] [DEBUG] (s) workDirectory =
.../projects/lucene/mahout/mahout-clean/target/assembly/work
On Oct 23, 2009, at 8:54 PM, Benson Margulies wrote:
https://svn.apache.org/repos/asf/cxf/trunk/distribution/pom.xml
It's not in a profile here, since we condition the entire
distribution
module on a release profile. It should work just the same if the
plugin spec is inside a profile.
I note that ours has only config in the execution, none at top-
level.
mvn -X might also be informative.
On Fri, Oct 23, 2009 at 5:12 PM, Grant Ingersoll
<[email protected]>wrote:
Hey Benson,
Do you know how to turn this on the release profile?
I put in:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptorRefs>
<descriptorRef>project</descriptorRef>
</descriptorRefs>
<tarLongFileMode>gnu</tarLongFileMode>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<!-- this is used for inheritance merges -->
<phase>package</phase>
<!-- append to the packaging phase. -->
<goals>
<goal>single</goal>
<!-- goals == mojos -->
</goals>
<configuration>
<tarLongFileMode>gnu</tarLongFileMode>
</configuration>
</execution>
</executions>
</plugin>
but I am still getting:
Failed to create assembly: Error creating assembly archive project:
Problem creating TAR: request to write '0' bytes exceeds size in
header
of
'-1535663957' bytes
-Grant
On Jul 16, 2009, at 10:48 AM, Benson Margulies wrote:
Do you have long mode turned on?
On Thu, Jul 16, 2009 at 10:01 AM, Grant Ingersoll<[email protected]
>
wrote:
Anyone else seeing: Failed to create assembly: Error creating
assembly
archive project: Problem creating TAR: request to write '0' bytes
exceeds
size in header of '-1535663957' bytes
when doing mvn install. I know the problem has to do with
TAR. I'm
just
wondering if we should switch to JAR/Zip packaging only,
instead of
tarballs.
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids)
using
Solr/Lucene:
http://www.lucidimagination.com/search
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids)
using Solr/Lucene:
http://www.lucidimagination.com/search
