[
https://issues.jboss.org/browse/JBIDE-16249?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-16249:
---------------------------------------
[~fbricon] I have this for jboss nexus:
{code}
<profile>
<id>jboss-maven-repos</id>
<repositories>
<repository>
<id>jboss-releases</id>
<
url>https://repository.jboss.org/nexus/content/repositories/releases&l...
<releases>
<enabled>true</enabled>
</releases> <!-- Default: true -->
</repository>
<repository>
<id>jboss-snapshots-repository</id>
<
url>https://repository.jboss.org/nexus/content/repositories/snapshots/...
<snapshots>
<enabled>true</enabled>
</snapshots> <!-- Default: false -->
</repository>
</repositories>
</profile>
{code}
So yes, it is slightly different. I will try the one you suggest.
Offline groovy script not working - FileNotFoundException
----------------------------------------------------------
Key: JBIDE-16249
URL:
https://issues.jboss.org/browse/JBIDE-16249
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, project-examples
Affects Versions: 4.1.1.CR1
Environment: JBDS 7.1.0.CR1a B560
OS X
Groovy Version: 2.1.8 JVM: 1.7.0_45 Vendor: Oracle Corporation OS: Mac OS X (installed
via mac ports)
Reporter: Martin Malina
Assignee: Fred Bricon
Fix For: 4.1.2.CR1
Attachments: groovy.log
I tried to run the offline examples groovy script today (Preferences -> JBoss Tools
-> Project Examples -> Offline Support).
When I ran the script I saw a couple of errors along the way, see at the end of email. I
was told that it could have to do with WFK 2.4 not being available in the online repo
yet.
But ultimately the script failed this exception:
java.io.FileNotFoundException:
/Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-javaee6-webapp-blank-archetype/my-jboss-javaee6-webapp-blank-archetype
I had jboss nexus and
http://maven.repository.redhat.com/techpreview/all/ in my
settings.xml. After the script finished, the offline dir was 536M big.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira