Maven 1.x Site Plugin

site:ftpdeploy does nothing

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.5.2, 1.6
  • Fix Version/s: 1.6.1
  • Component/s: plugin
  • Labels:
    None
  • Environment:
    Maven 1.0.2 + site plugin 1.6 + Windows XP (for maven) + JDK 1.4.2_06 + AIX 5.2 (web server)
  • Number of attachments :
    2

Description

If I try to publish the site with ftp nothing happens.
Here is the trace :
xdoc:init:

site:init:

site:local-deploy-init:
[echo]
site clean = false
siteDirectory = /XXXXX/intranet

site:remote-deploy-init:
[echo]
siteAddress = XXXXX
siteUsername = XXXXX

attaining goal build:end

The same problem was reported on the users list.

Attachments

  1. Text File
    MPSITE-22.diff
    01/Jun/05 9:30 AM
    2 kB
    Arnaud Heritier
  2. Text File
    MPSITE-22-full-log.txt
    01/Feb/05 8:20 AM
    16 kB
    Arnaud Heritier

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Arnaud Heritier added a comment -

maven -X log

Show
Arnaud Heritier added a comment - maven -X log
Hide
Permalink
Jason Taft added a comment -

Maven 1.0.2 is using ANT 1.5.3-1, which depends on (among others) the NetComponents.jar (http://www.savarese.org/oro/index.html).

Looking at your ${maven.home}/bin/forehead.conf file, you will see that the [root] classloader loads the ANT libraries, while the [root.maven] classloader is loading all other JARs in the lib and lib/endorsed directories.

Since classloaders can only see up the class loading hierarchy, the ANT classes can't see those classes loaded as a result of the <dependencies> tags within your projects.

SOLUTION (may be others?):
Get a copy of NetComponents.jar and load it in the [root] classloader

Note: Mave doesn't use the environmental CLASSPATH variable, so adding NetComponents.jar there won't work.

Show
Jason Taft added a comment - Maven 1.0.2 is using ANT 1.5.3-1, which depends on (among others) the NetComponents.jar (http://www.savarese.org/oro/index.html). Looking at your ${maven.home}/bin/forehead.conf file, you will see that the [root] classloader loads the ANT libraries, while the [root.maven] classloader is loading all other JARs in the lib and lib/endorsed directories. Since classloaders can only see up the class loading hierarchy, the ANT classes can't see those classes loaded as a result of the <dependencies> tags within your projects. SOLUTION (may be others?): Get a copy of NetComponents.jar and load it in the [root] classloader Note: Mave doesn't use the environmental CLASSPATH variable, so adding NetComponents.jar there won't work.
Hide
Permalink
Jason Taft added a comment -

I couldn't get the NetComponents.jar dependency to load into the root classloader using the following in my <dependency> tag in the POM:

<properties>
<classloader>root</classloader>
</properties>

Does anyone know if this dependecy property is valid and implemented?

Show
Jason Taft added a comment - I couldn't get the NetComponents.jar dependency to load into the root classloader using the following in my <dependency> tag in the POM: <properties> <classloader>root</classloader> </properties> Does anyone know if this dependecy property is valid and implemented?
Hide
Permalink
Jason Taft added a comment -

I couldn't get the NetComponents.jar dependency to load into the root classloader using the following in my <dependency> tag in the POM:

<properties>
<classloader>root</classloader>
</properties>

Does anyone know if this dependecy property is valid and implemented?

Show
Jason Taft added a comment - I couldn't get the NetComponents.jar dependency to load into the root classloader using the following in my <dependency> tag in the POM: <properties> <classloader>root</classloader> </properties> Does anyone know if this dependecy property is valid and implemented?
Hide
Permalink
Arnaud Heritier added a comment -

Yes it is supposed to work.
It's often used in plugins.

Show
Arnaud Heritier added a comment - Yes it is supposed to work. It's often used in plugins.
Hide
Permalink
Geoffrey De Smet added a comment -

site:ftpdeploy does nothing with me either.
No exception, no output, no ftping.

Using the ftp tag in maven.xml doesn't work either.

Local ftp from the command line works.

Show
Geoffrey De Smet added a comment - site:ftpdeploy does nothing with me either. No exception, no output, no ftping. Using the ftp tag in maven.xml doesn't work either. Local ftp from the command line works.
Hide
Permalink
Arnaud Heritier added a comment -

Fix for maven 1.1 (using ant 1.6.4)

Show
Arnaud Heritier added a comment - Fix for maven 1.1 (using ant 1.6.4)
Hide
Permalink
Arnaud Heritier added a comment -

Fixed for maven 1.1.

Show
Arnaud Heritier added a comment - Fixed for maven 1.1.
Hide
Permalink
Arnaud Heritier added a comment -

It must be documented that ftpdeploy will work only with maven 1.1. It is impossible to make it work with maven 1.0 because of the need of netComponents.

Show
Arnaud Heritier added a comment - It must be documented that ftpdeploy will work only with maven 1.1. It is impossible to make it work with maven 1.0 because of the need of netComponents.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.