[m2e-dev] Questions about the discovery catalog

["Thorsten Heit" <thorsten.heit@xxxxxx>]

Hi,

I'm working on updating my m2e connector plugin for
the axistools-maven-plugin to be compatible with newer m2e releases. After
reading the documentation in [1], I'm a bit puzzled of what to exactly
add/enter into a catalog entry. Ok, I can copy&paste one of the existing
entries in the connectors document ([2]) and change some of the XML elements,
but before doing something wrong:

Is there any description of connectors document XML
format? For example
- which elements are necessary and which optional?
- what meaning they have
- what to put into such an element
etc.pp.



Another question:

According to [1], I have to test the discovery catalog
before submitting a pull request. At home without using a settings.xml,
"mvn package" finished in around 6 minutes. Not really fast,
but well, it worked.

In our company I'm behind a firewall and have to use
the company's proxy to access websites. Therefore my settings.xml contains
entries so that Maven uses a Nexus OSS instance I have installed on a virtual
machine which itself talks to the outer world via our company proxy. Additionally
I have configured our company proxy directly in my settings.xml, and normally
all this works quite well. The problem I'm facing is that "mvn package"
took almost 46 minutes (!) until it finally finished:

(...)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] org.eclipse.m2e.discovery-directory ................
SUCCESS [  0.002 s]
[INFO] org.eclipse.m2e.discovery.oss ......................
SUCCESS [45:46 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------


On the console I see lots of messages such as:

(...)
Okt 22, 2014 10:59:43 AM org.apache.commons.httpclient.HttpMethodBase
readResponseBody
INFORMATION: Response content length is not known

These two lines appear lots of times, second per second.


(...)
org.sonatype.m2e.subclipse.feature.feature.group is
a group feature IU
Okt 22, 2014 11:01:59 AM org.apache.commons.httpclient.HttpMethodDirector
executeWithRetry
INFORMATION: I/O exception (java.net.ConnectException)
caught when processing request: Operation timed out
Okt 22, 2014 11:01:59 AM org.apache.commons.httpclient.HttpMethodDirector
executeWithRetry
INFORMATION: Retrying request
Okt 22, 2014 11:03:14 AM org.apache.commons.httpclient.HttpMethodDirector
executeWithRetry
INFORMATION: I/O exception (java.net.ConnectException)
caught when processing request: Operation timed out
Okt 22, 2014 11:03:14 AM org.apache.commons.httpclient.HttpMethodDirector
executeWithRetry
INFORMATION: Retrying request
Okt 22, 2014 11:04:29 AM org.apache.commons.httpclient.HttpMethodDirector
executeWithRetry
INFORMATION: I/O exception (java.net.ConnectException)
caught when processing request: Operation timed out
Okt 22, 2014 11:04:29 AM org.apache.commons.httpclient.HttpMethodDirector
executeWithRetry
(...)

When you look at the timestamps, it seems to me that
the packaging process ignores my proxy settings.

(...)
Okt 22, 2014 11:41:50 AM org.apache.commons.httpclient.HttpMethodBase
processCookieHeaders
WARNUNG: Invalid cookie header: "sf_mirror_attempt="lportal:netcologne:Liferay%20IDE/2.1.1%20GA2/updatesite/p2.index";
expires=120; Path=/". Unable to parse expiration date parameter: 120
^[[BOkt 22, 2014 11:41:55 AM org.apache.commons.httpclient.HttpMethodBase
processCookieHeaders
WARNUNG: Invalid cookie header: "sf_mirror_attempt="lportal:garr:Liferay%20IDE/2.1.1%20GA2/updatesite/compositeArtifacts.xml";
expires=120; Path=/". Unable to parse expiration date parameter: 120
Okt 22, 2014 11:42:13 AM org.apache.commons.httpclient.HttpMethodBase
processCookieHeaders
WARNUNG: Invalid cookie header: "sf_mirror_attempt="lportal:heanet:Liferay%20IDE/2.1.1%20GA2/updatesite/tools/artifacts.jar";
expires=120; Path=/". Unable to parse expiration date parameter: 120
(...)

As far as I remember I also saw these messages at
home, so I assume this is simply a warning that can be ignored...



Any idea why "mvn package" needs such a
long time in our company?



[1] https://github.com/takari/m2e-discovery-catalog
[2] https://github.com/takari/m2e-discovery-catalog/blob/master/org.eclipse.m2e.discovery.oss/src/main/resources-filtered/connectors.xml


Regards

Thorsten Heit