[jira] Commented: (IVY-896) Add GDF as a report output format
[ https://issues.apache.org/jira/browse/IVY-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628846#action_12628846 ] Xavier Hanin commented on IVY-896: -- Hi Nascif, Thanks for sharing this with Ivy community! I like the power this tool gives to dependency analysis. I also like the original graph image, I may do a t-shirt with it :-) Add GDF as a report output format - Key: IVY-896 URL: https://issues.apache.org/jira/browse/IVY-896 Project: Ivy Issue Type: New Feature Components: Core Affects Versions: 2.0.0-beta-1 Reporter: Nascif Abousalh-Neto Priority: Minor Fix For: unspecified Attachments: gdf.xsl, j1.jpg, sp.jpg We have been dealing with some very large graphs here (thousands of nodes, tens of thousands of edges) and the information density is so high that the graph visualization tools supported by Ivy, GraphViz and yED, were not up to the task. Then we found out about GUESS (http://graphexploration.cond.org/), which takes a novel approach which combines visualization support (using JUNG, an excellent library in itself) with a DSL for graph manipulation based on Jython. This way a user can issue commands and run scripts that manipulate the graph contents with immediate visual feedback. We have been using it and has proven to be a great match for our use cases. GUESS claims to suport graphml but it was not able to parse the graphml report generated by Ivy. So I coded an XSL that creates GDF from the Ivy resolution report XML. Besides working :-) this method keeps the relevant (but non-visual) attributes from the original report in the GDF as well. These can be later used in GUESS to group nodes, create convex hulls, calculate metrics, and so on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-897) Add VPF as a report output format
[
https://issues.apache.org/jira/browse/IVY-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628847#action_12628847
]
Xavier Hanin commented on IVY-897:
--
Nice trick, thanks for sharing! I'm not sure how to include it though, maybe it
would better be kept as a resource for those who want to achieve the same
thing. Therefore maybe a short article on the wiki would be better for the
benefit of the community?
Add VPF as a report output format
-
Key: IVY-897
URL: https://issues.apache.org/jira/browse/IVY-897
Project: Ivy
Issue Type: New Feature
Components: Core
Affects Versions: 2.0.0-beta-1
Reporter: Nascif Abousalh-Neto
Priority: Minor
Fix For: unspecified
Attachments: vpf.xsl
One of the best practices in the use of Ivy for large organizations is to
replace all the revision values in the ivy.xml files with properties.
dependency name=my.module revision=${my.module.revision} ... /
This approach allows an administrator to control all revisions values used by
all modules in one single place - a Version Property File (or VPF for short).
This way versions can be controlled in a uniform way, with minimum
maintenance and reduced chance of error. For example, you can upgrade all
your modules dependencies from Log4J 3.5 to 4.0 with one single line change -
and be sure that you didn't forget any of them behind.
Creating and maintaining VPFs is not trival though. One way to automate the
process is to harvest the module names and their latest versions from the
repository, using the repreport task to create a resolution report for the
entire repo and then converting it to a property file format using a XSL
spreadsheet (attached).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
svn commit: r692657 - /ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/.project
Author: hibou Date: Sat Sep 6 08:04:27 2008 New Revision: 692657 URL: http://svn.apache.org/viewvc?rev=692657view=rev Log: Add of checkstyle nature to the project Modified: ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/.project Modified: ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/.project URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/.project?rev=692657r1=692656r2=692657view=diff == --- ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/.project (original) +++ ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/.project Sat Sep 6 08:04:27 2008 @@ -1,46 +1,52 @@ -?xml version=1.0 encoding=UTF-8? -!-- - Licensed to the Apache Software Foundation (ASF) under one - or more contributor license agreements. See the NOTICE file - distributed with this work for additional information - regarding copyright ownership. The ASF licenses this file - to you under the Apache License, Version 2.0 (the - License); you may not use this file except in compliance - with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, - software distributed under the License is distributed on an - AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY - KIND, either express or implied. See the License for the - specific language governing permissions and limitations - under the License. --- -projectDescription - nameorg.apache.ivyde.eclipse/name - comment/comment - projects - /projects - buildSpec - buildCommand - nameorg.eclipse.jdt.core.javabuilder/name - arguments - /arguments - /buildCommand - buildCommand - nameorg.eclipse.pde.ManifestBuilder/name - arguments - /arguments - /buildCommand - buildCommand - nameorg.eclipse.pde.SchemaBuilder/name - arguments - /arguments - /buildCommand - /buildSpec - natures - natureorg.eclipse.pde.PluginNature/nature - natureorg.eclipse.jdt.core.javanature/nature - /natures -/projectDescription +?xml version=1.0 encoding=UTF-8? +!-- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + License); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +-- +projectDescription + nameorg.apache.ivyde.eclipse/name + comment/comment + projects + /projects + buildSpec + buildCommand + nameorg.eclipse.jdt.core.javabuilder/name + arguments + /arguments + /buildCommand + buildCommand + nameorg.eclipse.pde.ManifestBuilder/name + arguments + /arguments + /buildCommand + buildCommand + nameorg.eclipse.pde.SchemaBuilder/name + arguments + /arguments + /buildCommand + buildCommand + namecom.atlassw.tools.eclipse.checkstyle.CheckstyleBuilder/name + arguments + /arguments + /buildCommand + /buildSpec + natures + natureorg.eclipse.pde.PluginNature/nature + natureorg.eclipse.jdt.core.javanature/nature + naturecom.atlassw.tools.eclipse.checkstyle.CheckstyleNature/nature + /natures +/projectDescription
svn commit: r692658 [3/3] - in /ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde: common/completion/ common/ivyfile/ common/ivysettings/ common/model/ eclipse/ eclipse/cpcontaine
Modified:
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLDoubleClickStrategy.java
URL:
http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLDoubleClickStrategy.java?rev=692658r1=692657r2=692658view=diff
==
---
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLDoubleClickStrategy.java
(original)
+++
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLDoubleClickStrategy.java
Sat Sep 6 08:06:53 2008
@@ -30,8 +30,9 @@
public void doubleClicked(ITextViewer part) {
int pos = part.getSelectedRange().x;
-if (pos 0)
+if (pos 0) {
return;
+}
fText = part;
@@ -54,13 +55,15 @@
pos -= 2;
continue;
}
-if (c == Character.LINE_SEPARATOR || c == '\')
+if (c == Character.LINE_SEPARATOR || c == '\') {
break;
+}
--pos;
}
-if (c != '\')
+if (c != '\') {
return false;
+}
startPos = pos;
@@ -70,12 +73,14 @@
while (pos length) {
c = doc.getChar(pos);
-if (c == Character.LINE_SEPARATOR || c == '\')
+if (c == Character.LINE_SEPARATOR || c == '\') {
break;
+}
++pos;
}
-if (c != '\')
+if (c != '\') {
return false;
+}
endPos = pos;
@@ -103,8 +108,9 @@
while (pos = 0) {
c = doc.getChar(pos);
-if (!Character.isJavaIdentifierPart(c))
+if (!Character.isJavaIdentifierPart(c)) {
break;
+}
--pos;
}
@@ -115,8 +121,9 @@
while (pos length) {
c = doc.getChar(pos);
-if (!Character.isJavaIdentifierPart(c))
+if (!Character.isJavaIdentifierPart(c)) {
break;
+}
++pos;
}
Modified:
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLEditor.java
URL:
http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLEditor.java?rev=692658r1=692657r2=692658view=diff
==
---
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLEditor.java
(original)
+++
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLEditor.java
Sat Sep 6 08:06:53 2008
@@ -32,8 +32,8 @@
public XMLEditor(IvyContentAssistProcessor processor) {
super();
colorManager = new ColorManager();
-_configuration = new XMLConfiguration(colorManager, processor);
-setSourceViewerConfiguration(_configuration);
+configuration = new XMLConfiguration(colorManager, processor);
+setSourceViewerConfiguration(configuration);
setDocumentProvider(new XMLDocumentProvider());
}
@@ -45,7 +45,7 @@
private static final String CONTENTASSIST_PROPOSAL_ID =
org.apache.ivyde.ContentAssistProposal;
-private XMLConfiguration _configuration;
+private XMLConfiguration configuration;
protected void createActions() {
super.createActions();
@@ -65,6 +65,6 @@
}
public void setFile(IFile file) {
-_configuration.setFile(file);
+configuration.setFile(file);
}
}
Modified:
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLPartitionScanner.java
URL:
http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLPartitionScanner.java?rev=692658r1=692657r2=692658view=diff
==
---
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLPartitionScanner.java
(original)
+++
ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/ui/editors/xml/XMLPartitionScanner.java
Sat Sep 6 08:06:53 2008
@@ -24,11 +24,11 @@
import org.eclipse.jface.text.rules.Token;
public class XMLPartitionScanner extends RuleBasedPartitionScanner {
-public final static String XML_DEFAULT = __xml_default;
+public static final String XML_DEFAULT = __xml_default;
-public final static String XML_COMMENT = __xml_comment;
+public static final
[jira] Resolved: (IVYDE-90) IvyDE does not do property value expansion
[
https://issues.apache.org/jira/browse/IVYDE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-90.
--
Resolution: Duplicate
IvyDE does not do property value expansion
--
Key: IVYDE-90
URL: https://issues.apache.org/jira/browse/IVYDE-90
Project: IvyDE
Issue Type: Bug
Components: classpath container
Affects Versions: 2.0.0.alpha1
Environment: Eclipse 3.3.1
MyEclipse 6.0.1
Aptana 1.1.6
Ivy/IvyDE plugins from xoocode
Reporter: Michael Laccetti
Attachments: IVYDE-90_patch.zip
If I create an Ivy properties file with the variables defined in them, and
then reference those variables in the built script, Ivy via Ant will pick
them up, and inject the correct information. However, the same does not go
for IvyDE; it conks out trying to retrieve
something-something-${lala}.ext
Sample ivy.roperties
{noformat}
spring.version=2.5.3
{noformat}
Sample ivysettings.xml
{code:xml}
ivysettings
properties file=ivy.properties /
/ivysettings
{code}
Sample ivy.xml
{code:xml}
ivy-module version=2.0
info organisation=com.cryptologic module=OCL /
dependencies
!-- Spring Dependencies --
dependency org=org.springframework name=spring-core
rev=${spring.version} /
/dependencies
/ivy-module
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-90) IvyDE does not do property value expansion
[
https://issues.apache.org/jira/browse/IVYDE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1262#action_1262
]
Nicolas Lalevée commented on IVYDE-90:
--
About the svn repository path, it is referenced in that
[page|http://ant.apache.org/ivy/ivyde/history/latest-milestone/build.html],
under the Building paragraph, but I have to admit it is not clear at all. I
will make it more visible, and add a paragraph about it in the download page.
By the way, the svn is there:
https://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk
About your issue, so it is clearly a duplicate of IVYDE-13.
IvyDE does not do property value expansion
--
Key: IVYDE-90
URL: https://issues.apache.org/jira/browse/IVYDE-90
Project: IvyDE
Issue Type: Bug
Components: classpath container
Affects Versions: 2.0.0.alpha1
Environment: Eclipse 3.3.1
MyEclipse 6.0.1
Aptana 1.1.6
Ivy/IvyDE plugins from xoocode
Reporter: Michael Laccetti
Attachments: IVYDE-90_patch.zip
If I create an Ivy properties file with the variables defined in them, and
then reference those variables in the built script, Ivy via Ant will pick
them up, and inject the correct information. However, the same does not go
for IvyDE; it conks out trying to retrieve
something-something-${lala}.ext
Sample ivy.roperties
{noformat}
spring.version=2.5.3
{noformat}
Sample ivysettings.xml
{code:xml}
ivysettings
properties file=ivy.properties /
/ivysettings
{code}
Sample ivy.xml
{code:xml}
ivy-module version=2.0
info organisation=com.cryptologic module=OCL /
dependencies
!-- Spring Dependencies --
dependency org=org.springframework name=spring-core
rev=${spring.version} /
/dependencies
/ivy-module
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (IVYDE-90) IvyDE does not do property value expansion
[
https://issues.apache.org/jira/browse/IVYDE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée reopened IVYDE-90:
--
oops, reopening, Will's issue is about IVYDE-13, but not the original issue
reported by Michael.
IvyDE does not do property value expansion
--
Key: IVYDE-90
URL: https://issues.apache.org/jira/browse/IVYDE-90
Project: IvyDE
Issue Type: Bug
Components: classpath container
Affects Versions: 2.0.0.alpha1
Environment: Eclipse 3.3.1
MyEclipse 6.0.1
Aptana 1.1.6
Ivy/IvyDE plugins from xoocode
Reporter: Michael Laccetti
Attachments: IVYDE-90_patch.zip
If I create an Ivy properties file with the variables defined in them, and
then reference those variables in the built script, Ivy via Ant will pick
them up, and inject the correct information. However, the same does not go
for IvyDE; it conks out trying to retrieve
something-something-${lala}.ext
Sample ivy.roperties
{noformat}
spring.version=2.5.3
{noformat}
Sample ivysettings.xml
{code:xml}
ivysettings
properties file=ivy.properties /
/ivysettings
{code}
Sample ivy.xml
{code:xml}
ivy-module version=2.0
info organisation=com.cryptologic module=OCL /
dependencies
!-- Spring Dependencies --
dependency org=org.springframework name=spring-core
rev=${spring.version} /
/dependencies
/ivy-module
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
svn commit: r692672 - /ant/ivy/ivyde/trunk/doc/build.html
Author: hibou Date: Sat Sep 6 09:09:31 2008 New Revision: 692672 URL: http://svn.apache.org/viewvc?rev=692672view=rev Log: Make the svn URL more explicit Modified: ant/ivy/ivyde/trunk/doc/build.html Modified: ant/ivy/ivyde/trunk/doc/build.html URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/build.html?rev=692672r1=692671r2=692672view=diff == --- ant/ivy/ivyde/trunk/doc/build.html (original) +++ ant/ivy/ivyde/trunk/doc/build.html Sat Sep 6 09:09:31 2008 @@ -43,16 +43,21 @@ The IvyDE plugins depends on the Ivy 2.0 OSGi bundle. So the Ivy bundle have to be installed in the Eclipse installation before starting the build. You can get an officially released version of Ivy. Go to the a href=http://ant.apache.org/ivy/download.cgi;Ivy download page/a and get the binary distribution. You will find in the zip the jar ivy-2.X.Y-Z.jar. -Note: due to a href=https://issues.apache.org/jira/browse/IVY-802;a bug in the build script of Ivy/a, the OSGi version of Ivy is 0.0.0 for every version older than the 2.0.0-RC1. So a repackaging is needed. If you get the sources (which includes the build system), you can automatically install the repackaged 2.0.0-beta2 into you Eclipse install by running codeant install-ivy/code. +Note: due to a href=https://issues.apache.org/jira/browse/IVY-802;a bug in the build script of Ivy/a, the OSGi version of Ivy is 0.0.0 for every version older than the 2.0.0-RC1. So a repackaging is needed. If you get the sources (which includes the build system), you can automatically install the repackaged 2.0.0-beta2 into you Eclipse install by running: codeant install-ivy/code You can also build it from the sources (from a href=https://svn.apache.org/repos/asf/ant/ivy/core/trunk/;subversion/a or from the a href=http://ant.apache.org/ivy/download.cgi;releases/a). In the build/artifact folder you should then find the bundle org.apache.ivy_2.X.Y-Z.jar. Actually every Ivy jar is an OSGi bundle. So just copy it in your Eclipse install: -codecp XX.jar $ECLIPSE_HOME/plugins/org.apache.ivy_2.X.Y-Z.jar/code +codecp XX.jar $ECLIPSE_HOME/plugins/org.apache.ivy_2.X.Y-Z.jar/code h1Building/h1 -First somehow you got some sources, for instance from a href=https://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk/;subversion/a. +First somehow you got some sources, for instance from the ASF subversion repository: +code +svn co https://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk ivyde-trunk +/code +or get directly the released sources from the a href=../../download.cgi#sourcesdistribution/a. + And go into the root folder of the sources. In that folder you should see the builder, org.apache.ivyde.eclipse and org.apache.ivyde.feature folders. And run the build:
svn commit: r692674 - /ant/ivy/site/ivyde/download.html
Author: hibou Date: Sat Sep 6 09:10:29 2008 New Revision: 692674 URL: http://svn.apache.org/viewvc?rev=692674view=rev Log: Add a paragraph about how to get the sources from the svn repository Modified: ant/ivy/site/ivyde/download.html Modified: ant/ivy/site/ivyde/download.html URL: http://svn.apache.org/viewvc/ant/ivy/site/ivyde/download.html?rev=692674r1=692673r2=692674view=diff == --- ant/ivy/site/ivyde/download.html (original) +++ ant/ivy/site/ivyde/download.html Sat Sep 6 09:10:29 2008 @@ -25,7 +25,7 @@ /head body textarea id=xooki-source -The Apache IvyDE distribution is available as an a href=#updatesiteEclipse update site/a, but you can also download and install it a href=#manualmanually/a from one of our mirrors. We encourage you to a href=#verifyverify the integrity/a of the downloaded files using signatures downloaded from our main distribution directory. +The Apache IvyDE distribution is available as an a href=#updatesiteEclipse update site/a, but you can also download and install it a href=#manualmanually/a from one of our mirrors. We encourage you to a href=#verifyverify the integrity/a of the downloaded files using signatures downloaded from our main distribution directory. You are also invited to look to the a href=#svnASF subversion/a if you are interested into contributing to IvyDE. h1a name=updatesite/aUpdate site/h1 @@ -89,13 +89,20 @@ unzip org.apache.ivyde.feature-2.0.0.alpha1.zip /code -h2Full sources/h2 +h2a name=sources/aFull sources/h2 The source distribution contains the source files of the plugins, the features and the build system, so you will be able to reproduce the build that create the 2.0.0.alpha1 release. Download a href=[preferred]/ant/ivyde/2.0.0.alpha1/apache-ivyde-sources-2.0.0.alpha1.zipapache-ivyde-sources-2.0.0.alpha1.zip/a -h1a name=verifyVerify Releases/a/h1 +h1a name=svn/aSources from the version control system/h1 + +The IvyDE sources can be also found on the ASF Subversion repository. You can checkout the trunk by running the command +code +svn co https://svn.apache.org/repos/asf/ant/ivy/ivyde/trunk ivyde-trunk +/code + +h1a name=verify/aVerify Releases/h1 It is essential that you verify the integrity of the downloaded files using the PGP signature or the SHA1 or MD5 checksums. The checksums are not as strong indicators as the PGP signature. The PGP signatures can be verified using PGP or GPG. First download the a href=http://www.apache.org/dist/ant/KEYS;KEYS/a as well as the asc signature file for the particular distribution. Make sure you get these files from the a href=http://www.apache.org/dist/ant/ivyde;main distribution directory/a, rather than from a mirror. Then verify the signatures using
[jira] Commented: (IVY-818) Ivy ibiblio resolver chokes on variables while checking descriptor consistency
[
https://issues.apache.org/jira/browse/IVY-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628890#action_12628890
]
Shawn Zeller commented on IVY-818:
--
I had the same problem trying to use the grizzly project last night. From my
ivy settings xml file
ibiblio name=java-net-maven1
root=http://download.java.net/maven/1; pattern=${java.net.maven.pattern}
m2compatible=false/
ibiblio name=java-net-maven2
root=http://download.java.net/maven/2/; m2compatible=true /
and here's a depedency that has the problem
dependency org=com.sun.grizzly name=grizzly-servlet-webserver
rev=1.8.5.4 /
Ivy ibiblio resolver chokes on variables while checking descriptor consistency
--
Key: IVY-818
URL: https://issues.apache.org/jira/browse/IVY-818
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.0-RC1
Environment: Ubuntu 8.04, ivy svn rev: 657553
Reporter: Robert Newson
The ibiblio resolver in trunk has a new facility for parsing
maven-metadata.xml in order to find the latest snapshots. Unfortunately it
doesn't work if the version numbers in the poms are variables, that is, our
pom's have ${subproject-version} in them.
When encountering these, Ivy throws this;
java.text.ParseException: inconsistent module descriptor file found in
'http://mvn.mycompany.com/maven2/removed/1.2.0-RQA2-20080518.055623-736.pom':
bad revision: expected='1.2.0-RQA2-SNAPSHOT' found='${subproject-version}';
at
org.apache.ivy.plugins.resolver.BasicResolver.checkDescriptorConsistency(BasicResolver.java:575)
at
org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:252)
at
org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:417)
at
org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:124)
at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:169)
at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:257)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:610)
at
org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:696)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:618)
at
org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:501)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:233)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:191)
at org.apache.ivy.Ivy.resolve(Ivy.java:502)
at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:232)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
It seems Ivy verifies that the pom matches the metadata file, laudable in
itself, but doesn't know that ${subproject-version} expands to the expected
value. Setting that as a property did not help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVY-818) Ivy ibiblio resolver chokes on variables while checking descriptor consistency
[
https://issues.apache.org/jira/browse/IVY-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Coene reassigned IVY-818:
-
Assignee: Maarten Coene
Ivy ibiblio resolver chokes on variables while checking descriptor consistency
--
Key: IVY-818
URL: https://issues.apache.org/jira/browse/IVY-818
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.0-RC1
Environment: Ubuntu 8.04, ivy svn rev: 657553
Reporter: Robert Newson
Assignee: Maarten Coene
The ibiblio resolver in trunk has a new facility for parsing
maven-metadata.xml in order to find the latest snapshots. Unfortunately it
doesn't work if the version numbers in the poms are variables, that is, our
pom's have ${subproject-version} in them.
When encountering these, Ivy throws this;
java.text.ParseException: inconsistent module descriptor file found in
'http://mvn.mycompany.com/maven2/removed/1.2.0-RQA2-20080518.055623-736.pom':
bad revision: expected='1.2.0-RQA2-SNAPSHOT' found='${subproject-version}';
at
org.apache.ivy.plugins.resolver.BasicResolver.checkDescriptorConsistency(BasicResolver.java:575)
at
org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:252)
at
org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:417)
at
org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:124)
at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:169)
at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:257)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:610)
at
org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:696)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:618)
at
org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:501)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:233)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:191)
at org.apache.ivy.Ivy.resolve(Ivy.java:502)
at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:232)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
It seems Ivy verifies that the pom matches the metadata file, laudable in
itself, but doesn't know that ${subproject-version} expands to the expected
value. Setting that as a property did not help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
svn commit: r692729 - in /ant/ivy/core/trunk: ./ src/java/org/apache/ivy/plugins/parser/m2/ test/java/org/apache/ivy/plugins/parser/m2/
Author: maartenc
Date: Sat Sep 6 13:32:48 2008
New Revision: 692729
URL: http://svn.apache.org/viewvc?rev=692729view=rev
Log:
FIX: Ivy ibiblio resolver chokes on variables while checking descriptor
consistency (IVY-818)
Modified:
ant/ivy/core/trunk/CHANGES.txt
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorBuilder.java
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java
ant/ivy/core/trunk/test/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParserTest.java
ant/ivy/core/trunk/test/java/org/apache/ivy/plugins/parser/m2/test-parent-properties.pom
ant/ivy/core/trunk/test/java/org/apache/ivy/plugins/parser/m2/test-version.pom
Modified: ant/ivy/core/trunk/CHANGES.txt
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/CHANGES.txt?rev=692729r1=692728r2=692729view=diff
==
--- ant/ivy/core/trunk/CHANGES.txt (original)
+++ ant/ivy/core/trunk/CHANGES.txt Sat Sep 6 13:32:48 2008
@@ -111,6 +111,7 @@
- IMPROVEMENT: Add a memory cache for the module descriptor that are parsed
from the cache (IVY-883)
- IMPROVEMENT: Improve performance (IVY-872)
+- FIX: Ivy ibiblio resolver chokes on variables while checking descriptor
consistency (IVY-818)
- FIX: Enable consistent support of the configuration negation operator
(IVY-894) (thanks to Patrick Woodworth)
- FIX: add variable expansion in extra attributes (IVY-798)
- FIX: Invalid URL when using dynamic ranges (IVY-885)
Modified:
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorBuilder.java
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorBuilder.java?rev=692729r1=692728r2=692729view=diff
==
---
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorBuilder.java
(original)
+++
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorBuilder.java
Sat Sep 6 13:32:48 2008
@@ -328,7 +328,7 @@
public void addPlugin(PomDependencyMgt plugin) {
String pluginValue = plugin.getGroupId() + EXTRA_INFO_DELIMITER +
plugin.getArtifactId()
+ EXTRA_INFO_DELIMITER + plugin.getVersion();
-String pluginExtraInfo = (String)
ivyModuleDescriptor.getExtraInfo().get(maven.plugins);
+String pluginExtraInfo = (String)
ivyModuleDescriptor.getExtraInfo().get(m:maven.plugins);
if (pluginExtraInfo == null) {
pluginExtraInfo = pluginValue;
} else {
Modified:
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java?rev=692729r1=692728r2=692729view=diff
==
---
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java
(original)
+++
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java
Sat Sep 6 13:32:48 2008
@@ -111,10 +111,33 @@
PomModuleDescriptorBuilder mdBuilder = new
PomModuleDescriptorBuilder(this, res);
try {
-PomReader domReader = new PomReader(descriptorURL, res);
-
+PomReader domReader = new PomReader(descriptorURL, res);
domReader.setProperty(parent.version,
domReader.getParentVersion());
+ModuleDescriptor parentDescr = null;
+if (domReader.hasParent()) {
+//Is there any other parent properties?
+
+ModuleRevisionId parentModRevID = ModuleRevisionId.newInstance(
+domReader.getParentGroupId(),
+domReader.getParentArtifactId(),
+domReader.getParentVersion());
+ResolvedModuleRevision parentModule =
parseOtherPom(ivySettings,
+parentModRevID);
+if (parentModule != null) {
+parentDescr = parentModule.getDescriptor();
+} else {
+ Message.warn(impossible to load parent for +
descriptorURL + .
+ + Parent= + parentModRevID);
+}
+
+Map parentPomProps =
PomModuleDescriptorBuilder.extractPomProperties(parentDescr.getExtraInfo());
+for (Iterator iter = parentPomProps.entrySet().iterator();
iter.hasNext();) {
+Map.Entry prop = (Map.Entry) iter.next();
+domReader.setProperty((String) prop.getKey(), (String)
prop.getValue());
+}
+}
+
[jira] Resolved: (IVY-818) Ivy ibiblio resolver chokes on variables while checking descriptor consistency
[
https://issues.apache.org/jira/browse/IVY-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Coene resolved IVY-818.
---
Resolution: Fixed
Fix Version/s: 2.0-RC1
I've fixed the problem with the grizzly project, so I assume the original
problem will also be solved.
Please reopen if it is not the case.
Ivy ibiblio resolver chokes on variables while checking descriptor consistency
--
Key: IVY-818
URL: https://issues.apache.org/jira/browse/IVY-818
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.0-RC1
Environment: Ubuntu 8.04, ivy svn rev: 657553
Reporter: Robert Newson
Assignee: Maarten Coene
Fix For: 2.0-RC1
The ibiblio resolver in trunk has a new facility for parsing
maven-metadata.xml in order to find the latest snapshots. Unfortunately it
doesn't work if the version numbers in the poms are variables, that is, our
pom's have ${subproject-version} in them.
When encountering these, Ivy throws this;
java.text.ParseException: inconsistent module descriptor file found in
'http://mvn.mycompany.com/maven2/removed/1.2.0-RQA2-20080518.055623-736.pom':
bad revision: expected='1.2.0-RQA2-SNAPSHOT' found='${subproject-version}';
at
org.apache.ivy.plugins.resolver.BasicResolver.checkDescriptorConsistency(BasicResolver.java:575)
at
org.apache.ivy.plugins.resolver.BasicResolver.getDependency(BasicResolver.java:252)
at
org.apache.ivy.plugins.resolver.IBiblioResolver.getDependency(IBiblioResolver.java:417)
at
org.apache.ivy.plugins.resolver.ChainResolver.getDependency(ChainResolver.java:124)
at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:169)
at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:257)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:610)
at
org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:696)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:618)
at
org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:501)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:233)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:191)
at org.apache.ivy.Ivy.resolve(Ivy.java:502)
at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:232)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
It seems Ivy verifies that the pom matches the metadata file, laudable in
itself, but doesn't know that ${subproject-version} expands to the expected
value. Setting that as a property did not help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-671) Ivy version information doesn't fit on 1 line
[
https://issues.apache.org/jira/browse/IVY-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Coene resolved IVY-671.
---
Resolution: Won't Fix
Not really an issue...
Ivy version information doesn't fit on 1 line
-
Key: IVY-671
URL: https://issues.apache.org/jira/browse/IVY-671
Project: Ivy
Issue Type: Improvement
Components: Ant
Affects Versions: 2.0.0-beta-1
Reporter: Maarten Coene
When Ivy is loaded, the version is printed on the console.
For 2.0.0-beta1, this information doesn't fit on a single line (cfr the blank
line after ivy:info):
{code}
init-classpaths-with-ivy:
[ivy:info] :: Ivy 2.0.0-beta1 - 20071206070608 :: http://ant.apache.org/ivy/
::
:: loading settings :: file =
C:\working\repository\commons\lcm\ant_build\config
\ivy\ivysettings.xml
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-896) Add GDF as a report output format
[ https://issues.apache.org/jira/browse/IVY-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628932#action_12628932 ] Nascif Abousalh-Neto commented on IVY-896: -- Hi Xavier, You're welcome! And the T-shirt is a great idea, fun that you remembered! :-) I also added some Gython scripts to the GUESS site that were quite useful when dealing with Ivy-generated graphs: http://groups.google.com/group/guess-discuss/files You can link to them in the documentation if you add this feature to Ivy. I will attach here another file with scripts that are Ivy specific (like removing the all-caller node introduced by report and repreport). Add GDF as a report output format - Key: IVY-896 URL: https://issues.apache.org/jira/browse/IVY-896 Project: Ivy Issue Type: New Feature Components: Core Affects Versions: 2.0.0-beta-1 Reporter: Nascif Abousalh-Neto Priority: Minor Fix For: unspecified Attachments: gdf.xsl, j1.jpg, sp.jpg We have been dealing with some very large graphs here (thousands of nodes, tens of thousands of edges) and the information density is so high that the graph visualization tools supported by Ivy, GraphViz and yED, were not up to the task. Then we found out about GUESS (http://graphexploration.cond.org/), which takes a novel approach which combines visualization support (using JUNG, an excellent library in itself) with a DSL for graph manipulation based on Jython. This way a user can issue commands and run scripts that manipulate the graph contents with immediate visual feedback. We have been using it and has proven to be a great match for our use cases. GUESS claims to suport graphml but it was not able to parse the graphml report generated by Ivy. So I coded an XSL that creates GDF from the Ivy resolution report XML. Besides working :-) this method keeps the relevant (but non-visual) attributes from the original report in the GDF as well. These can be later used in GUESS to group nodes, create convex hulls, calculate metrics, and so on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-896) Add GDF as a report output format
[ https://issues.apache.org/jira/browse/IVY-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nascif Abousalh-Neto updated IVY-896: - Attachment: ivy.py Gython script that help to manipulate gdf files generated from Ivy reports. Add GDF as a report output format - Key: IVY-896 URL: https://issues.apache.org/jira/browse/IVY-896 Project: Ivy Issue Type: New Feature Components: Core Affects Versions: 2.0.0-beta-1 Reporter: Nascif Abousalh-Neto Priority: Minor Fix For: unspecified Attachments: gdf.xsl, ivy.py, j1.jpg, sp.jpg We have been dealing with some very large graphs here (thousands of nodes, tens of thousands of edges) and the information density is so high that the graph visualization tools supported by Ivy, GraphViz and yED, were not up to the task. Then we found out about GUESS (http://graphexploration.cond.org/), which takes a novel approach which combines visualization support (using JUNG, an excellent library in itself) with a DSL for graph manipulation based on Jython. This way a user can issue commands and run scripts that manipulate the graph contents with immediate visual feedback. We have been using it and has proven to be a great match for our use cases. GUESS claims to suport graphml but it was not able to parse the graphml report generated by Ivy. So I coded an XSL that creates GDF from the Ivy resolution report XML. Besides working :-) this method keeps the relevant (but non-visual) attributes from the original report in the GDF as well. These can be later used in GUESS to group nodes, create convex hulls, calculate metrics, and so on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-897) Add VPF as a report output format
[
https://issues.apache.org/jira/browse/IVY-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628934#action_12628934
]
Nascif Abousalh-Neto commented on IVY-897:
--
Hi Xavier,
It sure can be kept stand-alone and called with any XSLT tool. But that means
the user has to go over the extra work to provide the glue to find the
resolved report in the cache and then doing the transformation.
What I did was to clone the repreport task and add new methods to enable vpf as
an output option, just like you already have for graphml and dot:
if (vpf) {
genvpf(cacheMgr, md.getModuleRevisionId().getOrganisation(), md
.getModuleRevisionId().getName());
}
private void genvpf(ResolutionCacheManager cache, String organisation,
String module)
throws IOException {
gen(cache, organisation, module,
getLocalStylePath(cache.getResolutionCacheRoot(), /vpf.xsl), vpf);
}
But I the real important change I made to repreport was exposing the download
option from ResolverOptions. Running repreport as is was blowing away my disk
quota!
ResolveOptions ro = new ResolveOptions()
.setDownload(download)
.setResolveId(resolveId)
.setCache(ivy.getCacheManager(cache))
.setValidate(doValidate(settings));
But if you meant integration of the vpf files with the resolution process, the
trick is to include it with the properties command in your ivysettings:
ivysettings
settings defaultResolver=${default.resolver} /
properties file=${vpf.file} /
Now the user has a the flexbility of dealing with versions in a centralized
way, by selecting the appropriate vpf.file. He even implement a global version
promotion mechanism.
Of course it is your call - a short article on the wiki would work as well.
Add VPF as a report output format
-
Key: IVY-897
URL: https://issues.apache.org/jira/browse/IVY-897
Project: Ivy
Issue Type: New Feature
Components: Core
Affects Versions: 2.0.0-beta-1
Reporter: Nascif Abousalh-Neto
Priority: Minor
Fix For: unspecified
Attachments: vpf.xsl
One of the best practices in the use of Ivy for large organizations is to
replace all the revision values in the ivy.xml files with properties.
dependency name=my.module revision=${my.module.revision} ... /
This approach allows an administrator to control all revisions values used by
all modules in one single place - a Version Property File (or VPF for short).
This way versions can be controlled in a uniform way, with minimum
maintenance and reduced chance of error. For example, you can upgrade all
your modules dependencies from Log4J 3.5 to 4.0 with one single line change -
and be sure that you didn't forget any of them behind.
Creating and maintaining VPFs is not trival though. One way to automate the
process is to harvest the module names and their latest versions from the
repository, using the repreport task to create a resolution report for the
entire repo and then converting it to a property file format using a XSL
spreadsheet (attached).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
