Please changed behaviour of maven-war-plugin and maven-assembly-plugin
war-plugin 2.3 and assembly-plugin 2.4 both learned the recompressZippedFiles flag, which has a default value of false. When this value is false, both plugins will sniff filers being added for the 4 byte ZIP header and avoid recompressing files that are already zipped. Selecting false as default doubles the performance of these (quite slow) plugins, at the risk of creating a somewhat larger archive file. This change of behaviour will be troublesome if you make uncompressed jar files by default and rely on war/assembly to zip them, in which case you may want to set recompressZippedFiles to true. It may also be a good idea to set recompressZippedFiles to true in a release profile. Kristian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Please note changed behaviour of maven-war-plugin and maven-assembly-plugin
The original message reads a whole lot better the subject is changed to please note. The original message was informational, it describes a change that has already been made. Kristian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using Struts2 OSGi plugin with GlassFish
Hi Martin.
In struts2-osgi-plugin.jar there is no .\META-INF\maven\plugin.xml file.
I assume you mean the .\struts-plugin.xml file? Also if I understand
correctly there is no existing implementation of the PackageProvider
which can work with GlassFish, I will just have to implement my own, is
that right?
On 08/01/2013 21:30, Martin Gainty wrote:
The beauty of implementing a maven-plugin is that all attributes of
the plugin are configurable
open struts2-osgi-plugin.jar
edit
.\META-INF\maven\plugin.xml
look for
bean name=osgi
type=com.opensymphony.xwork2.config.PackageProvider
class=org.apache.struts2.osgi.OsgiConfigurationProvider /
as long as your com.opensymphony.xwork2.config.PackageProvider (felix
provider) implements interfaces
com.opensymphony.xwork2.config.PackageProvider
org.osgi.framework.BundleListener
then substitute in the felix PackageProvider to class attribute at
bean name=osgi
type=com.opensymphony.xwork2.config.PackageProvider
class=org.apache.struts2.osgi.OsgiConfigurationProvider /
save .\META-INF\maven\plugin.xml
/
close
/
rejar
/
place struts2-osgi-plugin.jar back into lib folder (after saving
original as struts2-osgi-plugin.jar.original)
if you do not redirect the PackageProvider this Struts-osgi-Listener
will be called as seen here from Provider code
org.apache.struts2.osgi.OsgiConfigurationProvider
public class OsgiConfigurationProvider implements PackageProvider,
BundleListener {
private static final Logger LOG =
LoggerFactory.getLogger(OsgiConfigurationProvider.class);
private Configuration configuration;
private ObjectFactory objectFactory;
private OsgiHost osgiHost;
private BundleContext bundleContext;
private BundleAccessor bundleAccessor;
private boolean bundlesChanged = false;
private ServletContext servletContext;
public void init(Configuration configuration) throws
ConfigurationException {
osgiHost = (OsgiHost)
servletContext.getAttribute(StrutsOsgiListener.OSGI_HOST);
bundleContext = osgiHost.getBundleContext();
bundleAccessor.setBundleContext(bundleContext);
bundleAccessor.setOsgiHost(osgiHost);
this.configuration = configuration;
//this class loader interface can be used by other plugins to
lookup resources
//from the bundles. A temporary class loader interface is set
during other configuration
//loading as well
servletContext.setAttribute(ClassLoaderInterface.CLASS_LOADER_INTERFACE,
new BundleClassLoaderInterface());
}
where servletContext Listener is set to
org.apache.struts2.osgi.StrutsOsgiListener
public class StrutsOsgiListener implements ServletContextListener {
public static final String OSGI_HOST = __struts_osgi_host;
private FelixOsgiHost osgiHost;
public void contextInitialized(ServletContextEvent sce) {
ServletContext servletContext = sce.getServletContext();
osgiHost = new FelixOsgiHost();
servletContext.setAttribute(OSGI_HOST, osgiHost);
try {
osgiHost.init(servletContext);
} catch (Exception e) {
throw new StrutsException(Apache Felix failed to start, e);
}
}
org.apache.struts2.osgi.FelixOsgiHost init will be called
public void init(ServletContext servletContext) {
this.servletContext = servletContext;
startFelix();
}
protected void startFelix() {
//load properties from felix embedded file
Properties configProps = getProperties(default.properties);
// Copy framework properties from the system properties.
Main.copySystemProperties(configProps);
replaceSystemPackages(configProps);
//struts, xwork and felix exported packages
Properties strutsConfigProps =
getProperties(struts-osgi.properties);
addExportedPackages(strutsConfigProps, configProps);
//find bundles and adde em to autostart property
addAutoStartBundles(configProps);
// Bundle cache
String storageDir = System.getProperty(java.io.tmpdir) +
.felix-cache;
configProps.setProperty(Constants.FRAMEWORK_STORAGE, storageDir);
if (LOG.isDebugEnabled())
LOG.debug(Storing bundles at [#0], storageDir);
String cleanBundleCache =
getServletContextParam(struts.osgi.clearBundleCache, true);
if (true.equalsIgnoreCase(cleanBundleCache)) {
if (LOG.isDebugEnabled())
LOG.debug(Clearing bundle cache);
configProps.put(FelixConstants.FRAMEWORK_STORAGE_CLEAN,
FelixConstants.FRAMEWORK_STORAGE_CLEAN_ONFIRSTINIT);
}
//other properties
configProps.put(FelixConstants.SERVICE_URLHANDLERS_PROP, false);
configProps.put(FelixConstants.LOG_LEVEL_PROP,
getServletContextParam(struts.osgi.logLevel, 1));
configProps.put(FelixConstants.BUNDLE_CLASSPATH, .);
configProps.put(FelixConstants.FRAMEWORK_BEGINNING_STARTLEVEL,
Re: Javadoc aggregation doesn't use snapshots?
Anyone? This has become a blocking issue for me, and am quite surprised that it exists at all given that the project really isn't complicated. Would it help if I put the code on github so that people could look at it more easily? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: snapshot versions and classpath stored in manifest
Are you positive you are using jar plugin version 2.3? On Mon, Jan 7, 2013 at 11:26 AM, Anthony Dahanne anthony.daha...@gmail.comwrote: Hello all, I am using Maven 3 with Nexus 2. I am building a cli tool (let's call it cli) , which has dependencies on some other libraries (let's call them dependencyA and dependencyB) To make my cli tool work in every environment, I rely on the manifest classpath, generated with : plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin and then I package everything (cli and its dependencies) using an assembly my launcher script looks like : java -jar cli*.jar (the * is there so that I won't need to update the script for any versions) If I build everything locally, in version 1.1.0-SNAPSHOT, here is the manifest classpath entry : Class-Path: dependencyA-1.1.0-SNAPSHOT.jar dependencyB-1.1.0-S NAPSHOT.jar slf4j-jdk14-1.6.6.jar slf4j-api-1.6.6.jar locally, everything is fine Now, if I download the assembly, built by a CI tool and published to Nexus, the manifest is still the same, but look at the names of the dependencies : ~ ls lib/ cli-1.1.0-20130105.224257-7.jar dependencyA-1.1.0-20130105.224257-7.jar dependencyB-1.1.0-20130105.224257-7.jar As you can imagine, the cli won't find it's dependencies since their version does not match any more the manifest's (SNAPSHOT in the manifest, 1.1.0-20130105.224257-7 is what we have) It seems like this issue was fixed some time ago : http://jira.codehaus.org/browse/MJAR-28 Is is a regression ? Thanks a lot for your help! Anthony
Re: Javadoc aggregation doesn't use snapshots?
A JIRA might get more useful attention, pointing to github or whatever. On Wed, Jan 9, 2013 at 11:00 AM, org.apache.maven.u...@io7m.com wrote: Anyone? This has become a blocking issue for me, and am quite surprised that it exists at all given that the project really isn't complicated. Would it help if I put the code on github so that people could look at it more easily? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: assembly plugin logging anomaly
Hi Steve, I can't remember what notation system it uses, but its a different one than what is usually seen for unix like permissions. It comes from a component that the plugin uses to perform these operations. On 2013-01-07 21:49, Steve Cohen wrote: Using the assembly plugin I have a file set defined with fileMode644/fileMode directoryMode755/directoryMode This works correctly - the archive generated has the desired permissions. But the logging says [DEBUG] FileSet[outputDir/] dir perms 4 file perms 10 What notation system is this and why does the plugin report it this way in the log. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-release-plugin fails to tag on Linux but works on Windows...
I don't know if this is related to maven or SVN so hopefully this is relevant here. We use TFS as the source control system with SVNBridge non-Microsoft access. I had a stand-alone Jenkins CI server running on Windows that we had been using but recently I setup Jenkins on Linux (Ubuntu 12.10) in a master + 4 slave configuration. When I do a Maven Release from Jenkins on Windows, the process works correctly. When releasing on Linux, I get an error during the tagging phase. The odd thing is that it commits the modified POM with the release versions just fine. Here is the output from the release portion. Is there anything I'm missing about why it won't work on Linux but does on Windows? [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /home/tomcat7/.jenkins/jobs/ParentPOM (trunk)/workspace svn --username jvincent --password '*' --no-auth-cache --non-interactive commit --file /tmp/maven-scm-1181114510.commit --targets /tmp/maven-scm-670605008954785933-targets [INFO] Working directory: /home/tomcat7/.jenkins/jobs/ParentPom (trunk)/workspace [DEBUG] Sendingpom.xml *[DEBUG] Transmitting file data .* *[DEBUG] Committed revision 199107.* [INFO] Tagging release with the label ParentPom-1.29... [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true [DEBUG] ScmTagPhase :: scmTagParameters scmRevision 199107 [DEBUG] ScmTagPhase :: fileSet basedir = /home/tomcat7/.jenkins/jobs/ParentPom (trunk)/workspace; files = [] [DEBUG] SvnTagCommand :: scmTagParameters.remoteTagging : true [INFO] Executing: /bin/sh -c cd /home/tomcat7/.jenkins/jobs/ParentPom (trunk)/workspace *svn --username jvincent --password '*' --no-auth-cache --non-interactive copy --file /tmp/maven-scm-320768443.commit --revision 199107 http://svnbridge.mycompany.int:8083/ParentPom/ http://svnbridge.mycompany.int:8083/Tags/ParentPom/ParentPom-1.29* [INFO] Working directory: /home/tomcat7/.jenkins/jobs/ParentPom (trunk)/workspace *mojoFailed org.apache.maven.plugins:maven-release-plugin:2.3.2(default-cli) * projectFailed com.mycompany:ParentPom:1.29-SNAPSHOT sessionEnded [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:15.172s [INFO] Finished at: Wed Jan 09 15:56:48 MST 2013 [INFO] Final Memory: 8M/53M [INFO] Projects to build: [MavenProject: com.mycompany:ParentPom:1.29-SNAPSHOT @ /home/tomcat7/.jenkins/jobs/ParentPom (trunk)/workspace/pom.xml] [JENKINS] Archiving /home/tomcat7/.jenkins/jobs/ParentPom (trunk)/workspace/pom.xml to /home/tomcat7/.jenkins/jobs/ParentPom (trunk)/modules/com.mycompany$ParentPom/builds/2013-01-09_15-54-24/archive/com.mycompany/ParentPom/1.29-SNAPSHOT/ParentPom-1.29-SNAPSHOT.pom Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project ParentPom: Unable to tag SCM Provider message: The svn tag command failed. Command output: *svn: E170001: COPY of '/!svn/bc/199107/ParentPom': authorization failed: Could not authenticate to server: rejected Digest challenge ( http://svnbridge.mycompany.com:8083)* -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !!
RE: Using Struts2 OSGi plugin with GlassFish
correct
yes for all intents and purposes struts-osgi-plugin *is* a functional struts
plugin
in order to interface to maven (plexus framework) we'll need to
1) port these attributes to \META-INF\maven\plugin.xml
constant name=struts.objectFactory value=osgi /
constant name=struts.objectFactory.delegate value=struts /
constant name=struts.freemarker.manager.classname
value=org.apache.struts2.osgi.BundleFreemarkerManager /!-- TBD: which
FreemarkerManager to use with Maven 3.x --
constant name=struts.staticContentLoader
value=org.apache.struts2.osgi.loaders.StaticContentBundleResourceLoader
/!-- TBD: which StaticContentBundleResourceLoader to use with Maven 3.x --
constant name=struts.convention.action.includeJars
value=jar:file:.*?/bundles/.*?\.jar(!/)? / 2) convert Struts methods for
org.apache.struts2.osgi.OsgiUtil.java translateBundleURLToJarURLand or
org.apache.struts2.osgi.interceptor.OsgiInterceptor intercept method to goal
annotation which will extends AbstractMojo@goal buildStruts2OSGIMojo extends
org.apache.maven.plugin.AbstractMojo(execute method)
3)populate \META-INF\maven\plugin.xml
so..in order to participate in maven lifecycle ...
a)defaultGoal will be 'build'
b)default binding will bind to 'package' phase
community..what are we missing ?
Martin
__
...place long-winded disclaimer here... Date: Wed, 9 Jan 2013 09:37:02 +0200
From: christina.kasko...@eurodyn.com
To: mgai...@hotmail.com
CC: u...@struts.apache.org; users@maven.apache.org
Subject: Re: Using Struts2 OSGi plugin with GlassFish
Hi Martin.
In struts2-osgi-plugin.jar there is no .\META-INF\maven\plugin.xml file.
I assume you mean the .\struts-plugin.xml file? Also if I understand
correctly there is no existing implementation of the PackageProvider
which can work with GlassFish, I will just have to implement my own, is
that right?
On 08/01/2013 21:30, Martin Gainty wrote:
The beauty of implementing a maven-plugin is that all attributes of
the plugin are configurable
open struts2-osgi-plugin.jar
edit
.\META-INF\maven\plugin.xml
look for
bean name=osgi
type=com.opensymphony.xwork2.config.PackageProvider
class=org.apache.struts2.osgi.OsgiConfigurationProvider /
as long as your com.opensymphony.xwork2.config.PackageProvider (felix
provider) implements interfaces
com.opensymphony.xwork2.config.PackageProvider
org.osgi.framework.BundleListener
then substitute in the felix PackageProvider to class attribute at
bean name=osgi
type=com.opensymphony.xwork2.config.PackageProvider
class=org.apache.struts2.osgi.OsgiConfigurationProvider /
save .\META-INF\maven\plugin.xml
/
close
/
rejar
/
place struts2-osgi-plugin.jar back into lib folder (after saving
original as struts2-osgi-plugin.jar.original)
if you do not redirect the PackageProvider this Struts-osgi-Listener
will be called as seen here from Provider code
org.apache.struts2.osgi.OsgiConfigurationProvider
public class OsgiConfigurationProvider implements PackageProvider,
BundleListener {
private static final Logger LOG =
LoggerFactory.getLogger(OsgiConfigurationProvider.class);
private Configuration configuration;
private ObjectFactory objectFactory;
private OsgiHost osgiHost;
private BundleContext bundleContext;
private BundleAccessor bundleAccessor;
private boolean bundlesChanged = false;
private ServletContext servletContext;
public void init(Configuration configuration) throws
ConfigurationException {
osgiHost = (OsgiHost)
servletContext.getAttribute(StrutsOsgiListener.OSGI_HOST);
bundleContext = osgiHost.getBundleContext();
bundleAccessor.setBundleContext(bundleContext);
bundleAccessor.setOsgiHost(osgiHost);
this.configuration = configuration;
//this class loader interface can be used by other plugins to
lookup resources
//from the bundles. A temporary class loader interface is set
during other configuration
//loading as well
servletContext.setAttribute(ClassLoaderInterface.CLASS_LOADER_INTERFACE,
new BundleClassLoaderInterface());
}
where servletContext Listener is set to
org.apache.struts2.osgi.StrutsOsgiListener
public class StrutsOsgiListener implements ServletContextListener {
public static final String OSGI_HOST = __struts_osgi_host;
private FelixOsgiHost osgiHost;
public void contextInitialized(ServletContextEvent sce) {
ServletContext servletContext = sce.getServletContext();
osgiHost = new FelixOsgiHost();
servletContext.setAttribute(OSGI_HOST, osgiHost);
try {
osgiHost.init(servletContext);
} catch (Exception e) {
throw new StrutsException(Apache Felix failed to start, e);
}
}
Re: assembly plugin logging anomaly
On 01/09/2013 04:52 PM, Dennis Lundberg wrote: Hi Steve, I can't remember what notation system it uses, but its a different one than what is usually seen for unix like permissions. It comes from a component that the plugin uses to perform these operations. On 2013-01-07 21:49, Steve Cohen wrote: Using the assembly plugin I have a file set defined with fileMode644/fileMode directoryMode755/directoryMode This works correctly - the archive generated has the desired permissions. But the logging says [DEBUG] FileSet[outputDir/] dir perms 4 file perms 10 What notation system is this and why does the plugin report it this way in the log. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org I suppose I should look in the source. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Resolution of concurrent SNAPSHOT artifacts from multiple repositories
In case it helps, here are the remote metadata: http://maven.in.nuxeo.com/nexus/service/local/repo_groups/internal-snapshots/content/org/nuxeo/nuxeo-ecm/5.7-SNAPSHOT/maven-metadata.xml ?xml version=1.0 encoding=UTF-8? metadata modelVersion=1.1.0 groupIdorg.nuxeo/groupId artifactIdnuxeo-ecm/artifactId version5.7-SNAPSHOT/version versioning snapshot timestamp20130107.094030/timestamp buildNumber43/buildNumber /snapshot lastUpdated20130108004356/lastUpdated snapshotVersions snapshotVersion classifiersite/classifier extensionxml/extension value5.7-20130107.094030-43/value updated20130107094030/updated /snapshotVersion snapshotVersion extensionpom/extension value5.7-20130107.094030-43/value updated20130107094030/updated /snapshotVersion /snapshotVersions /versioning /metadata https://maven.nuxeo.org/nexus/service/local/repo_groups/public-snapshot/content/org/nuxeo/nuxeo-ecm/5.7-SNAPSHOT/maven-metadata.xml ?xml version=1.0 encoding=UTF-8? metadata modelVersion=1.1.0 groupIdorg.nuxeo/groupId artifactIdnuxeo-ecm/artifactId version5.7-SNAPSHOT/version versioning snapshot timestamp20130107.013731/timestamp buildNumber138/buildNumber /snapshot lastUpdated20130108004356/lastUpdated snapshotVersions snapshotVersion classifiersite/classifier extensionxml/extension value5.7-20130107.013731-138/value updated20130107013731/updated /snapshotVersion snapshotVersion extensionpom/extension value5.7-20130107.013731-138/value updated20130107013731/updated /snapshotVersion /snapshotVersions /versioning /metadata Le 09/01/2013 15:41, Julien CARSIQUE a écrit : Hi, I would like some help about the following SNAPSHOT resolution issue using Maven 2.2.1. The artifact org.nuxeo:nuxeo-ecm:5.7-SNAPSHOT:pom has been deployed in two repositories : * in public-snapshot at 1h37 * in internal-snapshots at 9h40 The issue is Maven resolves the version 5.7-20130107.013731-138 from repository public-snapshot which is older than the 5.7-20130107.094030-43 one from repository internal-snapshots. Even if the issue still looks like MNG-5008, I don't know if it has something to do with it. I don't know how to deeper analyze the problem. Any help is very welcome. Here are a stacktrace extract and the two corresponding metadata files. $ mvn validate -X ... [DEBUG] Retrieving parent-POM: org.nuxeo:nuxeo-ecm:pom:5.7-SNAPSHOT for project: null:nuxeo-addons-parent:pom:null from the repository. [DEBUG] Skipping disabled repository internal-releases *[INFO] snapshot org.nuxeo:nuxeo-ecm:5.7-SNAPSHOT: checking for updates from internal-snapshots* [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'internal-snapshots' with url: 'http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots'. [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Skipping disabled repository public *[INFO] snapshot org.nuxeo:nuxeo-ecm:5.7-SNAPSHOT: checking for updates from public-snapshot* [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'public-snapshot' with url: 'http://maven.nuxeo.org/nexus/content/groups/public-snapshot'. [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Skipping disabled repository central *[DEBUG] nuxeo-ecm: resolved to version 5.7-20130107.013731-138 from repository public-snapshot* ... ~/.m2/repository/org/nuxeo/nuxeo-ecm/5.7-SNAPSHOT/maven-metadata-*internal-snapshots*.xml ?xml version=1.0 encoding=UTF-8? metadata groupIdorg.nuxeo/groupId artifactIdnuxeo-ecm/artifactId version5.7-SNAPSHOT/version versioning snapshot timestamp*20130107.094030*/timestamp buildNumber*43*/buildNumber /snapshot lastUpdated20130108004356/lastUpdated /versioning /metadata ~/.m2/repository/org/nuxeo/nuxeo-ecm/5.7-SNAPSHOT/maven-metadata-*public-snapshot*.xml ?xml version=1.0 encoding=UTF-8? metadata groupIdorg.nuxeo/groupId artifactIdnuxeo-ecm/artifactId version5.7-SNAPSHOT/version versioning snapshot timestamp*20130107.013731*/timestamp buildNumber*138*/buildNumber /snapshot lastUpdated20130108004356/lastUpdated /versioning /metadata Thanks,
Resolution of concurrent SNAPSHOT artifacts from multiple repositories
Hi, I would like some help about the following SNAPSHOT resolution issue using Maven 2.2.1. The artifact org.nuxeo:nuxeo-ecm:5.7-SNAPSHOT:pom has been deployed in two repositories : * in public-snapshot at 1h37 * in internal-snapshots at 9h40 The issue is Maven resolves the version 5.7-20130107.013731-138 from repository public-snapshot which is older than the 5.7-20130107.094030-43 one from repository internal-snapshots. Even if the issue still looks like MNG-5008, I don't know if it has something to do with it. I don't know how to deeper analyze the problem. Any help is very welcome. Here are a stacktrace extract and the two corresponding metadata files. $ mvn validate -X ... [DEBUG] Retrieving parent-POM: org.nuxeo:nuxeo-ecm:pom:5.7-SNAPSHOT for project: null:nuxeo-addons-parent:pom:null from the repository. [DEBUG] Skipping disabled repository internal-releases *[INFO] snapshot org.nuxeo:nuxeo-ecm:5.7-SNAPSHOT: checking for updates from internal-snapshots* [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'internal-snapshots' with url: 'http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots'. [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Skipping disabled repository public *[INFO] snapshot org.nuxeo:nuxeo-ecm:5.7-SNAPSHOT: checking for updates from public-snapshot* [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'public-snapshot' with url: 'http://maven.nuxeo.org/nexus/content/groups/public-snapshot'. [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Skipping disabled repository central *[DEBUG] nuxeo-ecm: resolved to version 5.7-20130107.013731-138 from repository public-snapshot* ... ~/.m2/repository/org/nuxeo/nuxeo-ecm/5.7-SNAPSHOT/maven-metadata-*internal-snapshots*.xml ?xml version=1.0 encoding=UTF-8? metadata groupIdorg.nuxeo/groupId artifactIdnuxeo-ecm/artifactId version5.7-SNAPSHOT/version versioning snapshot timestamp*20130107.094030*/timestamp buildNumber*43*/buildNumber /snapshot lastUpdated20130108004356/lastUpdated /versioning /metadata ~/.m2/repository/org/nuxeo/nuxeo-ecm/5.7-SNAPSHOT/maven-metadata-*public-snapshot*.xml ?xml version=1.0 encoding=UTF-8? metadata groupIdorg.nuxeo/groupId artifactIdnuxeo-ecm/artifactId version5.7-SNAPSHOT/version versioning snapshot timestamp*20130107.013731*/timestamp buildNumber*138*/buildNumber /snapshot lastUpdated20130108004356/lastUpdated /versioning /metadata Thanks,
Re: Javadoc aggregation doesn't use snapshots?
On Wed, 9 Jan 2013 14:30:47 -0500 Benson Margulies bimargul...@gmail.com wrote: A JIRA might get more useful attention, pointing to github or whatever. Opened: https://jira.codehaus.org/browse/MJAVADOC-360 Regards, M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: snapshot versions and classpath stored in manifest
Hello Brian, So I triple checked, and I specified : (2.4 is the latest version) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.4/version /plugin in each of my modules, but still, if I : * in my cli project reactor : $ mvn clean deploy * clean the local repo : $ rm -rf ~/.m2/repository/com/terracotta/ * in the assembly module : $ mvn clean install -U I get : z:target anthony$ tar xvzf assembly-1.1.0-SNAPSHOT-bundle.tar.gz x cli-1.1.0-20130110.023006-1.jar x dependencyA-1.1.0-20130110.023002-1.jar x slf4j-jdk14-1.6.6.jar x slf4j-api-1.6.6.jar with the cli manifest having : Class-Path: dependencyA-1.1.0-SNAPSHOT.jar slf4j-jdk14-1.6.6.jar slf4j -api-1.6.6.jar I set up a very simple example and a nexus instance to reproduce this use case https://github.com/anthonydahanne/maven-manifest-and-assembly-bug Thanks for having a look, Anthony On Wed, Jan 9, 2013 at 1:40 PM, Brian Fox bri...@infinity.nu wrote: Are you positive you are using jar plugin version 2.3? On Mon, Jan 7, 2013 at 11:26 AM, Anthony Dahanne anthony.daha...@gmail.comwrote: Hello all, I am using Maven 3 with Nexus 2. I am building a cli tool (let's call it cli) , which has dependencies on some other libraries (let's call them dependencyA and dependencyB) To make my cli tool work in every environment, I rely on the manifest classpath, generated with : plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin and then I package everything (cli and its dependencies) using an assembly my launcher script looks like : java -jar cli*.jar (the * is there so that I won't need to update the script for any versions) If I build everything locally, in version 1.1.0-SNAPSHOT, here is the manifest classpath entry : Class-Path: dependencyA-1.1.0-SNAPSHOT.jar dependencyB-1.1.0-S NAPSHOT.jar slf4j-jdk14-1.6.6.jar slf4j-api-1.6.6.jar locally, everything is fine Now, if I download the assembly, built by a CI tool and published to Nexus, the manifest is still the same, but look at the names of the dependencies : ~ ls lib/ cli-1.1.0-20130105.224257-7.jar dependencyA-1.1.0-20130105.224257-7.jar dependencyB-1.1.0-20130105.224257-7.jar As you can imagine, the cli won't find it's dependencies since their version does not match any more the manifest's (SNAPSHOT in the manifest, 1.1.0-20130105.224257-7 is what we have) It seems like this issue was fixed some time ago : http://jira.codehaus.org/browse/MJAR-28 Is is a regression ? Thanks a lot for your help! Anthony
Re: Maven3 PDF-Plugin1.2 - How to disable or change the default generated pdf footer text?
I haven't tested this in a while but the pdf footer should be the same as the site footer, did you try this: http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html#Custom_footer HTH, -Lukas Thorsten Nieser wrote: Hi together, Hopefully anybody could give me short hint how to resolve my current problem. I use Maven3 and the Doxia Pdf-Plugin 1.2 to generate the documentation bundle of the project I currently work on. * org.apache.maven.plugins * maven-pdf-plugin * 1.2 The project shall be released under GPL v.3 to be compatible with the Apache Common license v.2 and so it's not really matching that the generated documentation pdf gets the following footer text added by default: © 2 0 1 3 , NAME . A L L R I G H T S R E S E R V E D. Rights aren't really reserved by me - it's copy left. Is there any possibility to change the content of the footer text line? Thanks for your efforts in advance! With best regards Thorsten - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
