maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hamma Myamma (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MECLIPSE-607) Provide a site archive for offline install
Date Sat, 10 Oct 2009 18:09:49 GMT
Provide a site archive for offline install
------------------------------------------

                 Key: MECLIPSE-607
                 URL: http://jira.codehaus.org/browse/MECLIPSE-607
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Bug
          Components: M2Eclipse support
         Environment: all platforms
            Reporter: Hamma Myamma


The lack of a site archive for offline m2Eclipse installs should be considered a bug.  The
main workaround suggested in JIRA MNGECLIPSE-858 does not work.

The rationale for a site archive of the m2Eclipse plugin is that internet access is not available
in every situation.  Corporate restrictions are one common issue, but a greater issue is the
need to perform software development in classified environments.  These environments do not
have internet access, and all development software introduced into the environment must be
scanned and approved.

The workaround suggested in the above JIRA is to use the "well-documented command line interface
for Eclipse update manager".  Fortunately someone added a link in the JIRA to the documentation
for this capability.  Unfortunately, this capability depends on the proper configuration and
operation of the m2Eclipse update site, which is not 100% reliable.

For example, I have run the following command on two separate occasions today:

java -jar plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar -application org.eclipse.update.core.standaloneUpdate
-command mirror -from http://m2eclipse.sonatype.org/update/ -to /tmp/m2mirror/

This command works initially, grabbing the first 60MB of the update site, then fails with
404 errors (the issue I'm seeing at the moment is "404 Not Found" for URL: http://m2eclipse.sonatype.org/update/plugins/org.eclipse.zest.core_1.0.0.v20080115.jar).


I believe the more professional approach to this problem is for the Maven team to add a "site
archive" package to the m2Eclipse build process (as do most other prominent Eclipse plugins).
 This would capture build errors within the maven team, allowing random developers to avoid
an hour of googling and command-line trial-and-error, only to discover that the Maven update
site is broken in regards to this requirement.


Building things is Maven's specialty, right?  Providing this capability should take one of
you guys about two hours, I'm guessing ...


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message