You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Kevin Gann (JIRA)" <ji...@apache.org> on 2009/03/04 15:37:56 UTC
[jira] Created: (IVY-1040) Ivy License Column not populating
Ivy License Column not populating
---------------------------------
Key: IVY-1040
URL: https://issues.apache.org/jira/browse/IVY-1040
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.0
Environment: Ubuntu 8.04. Java 1.6_10. x86.
Reporter: Kevin Gann
Populating the License column in the Ivy report. If my assumption that if the POM has the license data in the directory used it would pull the license information?
For example...
I have the dependency defined...
<dependency org="org.antlr" name="antlr" rev="3.1.1" />
Which is coming from...
http://repo1.maven.org/maven2/org/antlr/antlr/3.1.1/antlr-3.1.1.jar
If I look at the HTTP directory I see the POM which contains the license information.
http://repo2.maven.org/maven2/org/antlr/antlr/3.1.1/antlr-3.1.1.pom
But when my report generates I don't see the license column populated. Maybe I'm missing something?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-1040) Ivy License Column not populating
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene resolved IVY-1040.
--------------------------------
Resolution: Cannot Reproduce
Assignee: Maarten Coene
Works for me.
If I take a look at the generated report, I see 2 things:
- the antlr is taken from another repository ("central" instead of "default")
- the publication date in the report is the current time, which means there is no pom (or Ivy didn't find it) for the antlr library in your "central" repository. So if Ivy can't find the pom it can't fill in the license in the report.
Please reopen if you think I'm mistaken and it still doesn't work for you.
Maarten
> Ivy License Column not populating
> ---------------------------------
>
> Key: IVY-1040
> URL: https://issues.apache.org/jira/browse/IVY-1040
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.0
> Environment: Ubuntu 8.04. Java 1.6_10. x86.
> Reporter: Kevin Gann
> Assignee: Maarten Coene
> Attachments: ivy.xml, test-icsr-prototype-test-default.html
>
>
> Populating the License column in the Ivy report. If my assumption that if the POM has the license data in the directory used it would pull the license information?
> For example...
> I have the dependency defined...
> <dependency org="org.antlr" name="antlr" rev="3.1.1" />
> Which is coming from...
> http://repo1.maven.org/maven2/org/antlr/antlr/3.1.1/antlr-3.1.1.jar
> If I look at the HTTP directory I see the POM which contains the license information.
> http://repo2.maven.org/maven2/org/antlr/antlr/3.1.1/antlr-3.1.1.pom
> But when my report generates I don't see the license column populated. Maybe I'm missing something?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-1040) Ivy License Column not populating
Posted by "Kevin Gann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Gann updated IVY-1040:
----------------------------
Attachment: test-icsr-prototype-test-default.html
This is the html report file. It shows a license for the postgres library, but not antlr.
> Ivy License Column not populating
> ---------------------------------
>
> Key: IVY-1040
> URL: https://issues.apache.org/jira/browse/IVY-1040
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.0
> Environment: Ubuntu 8.04. Java 1.6_10. x86.
> Reporter: Kevin Gann
> Attachments: test-icsr-prototype-test-default.html
>
>
> Populating the License column in the Ivy report. If my assumption that if the POM has the license data in the directory used it would pull the license information?
> For example...
> I have the dependency defined...
> <dependency org="org.antlr" name="antlr" rev="3.1.1" />
> Which is coming from...
> http://repo1.maven.org/maven2/org/antlr/antlr/3.1.1/antlr-3.1.1.jar
> If I look at the HTTP directory I see the POM which contains the license information.
> http://repo2.maven.org/maven2/org/antlr/antlr/3.1.1/antlr-3.1.1.pom
> But when my report generates I don't see the license column populated. Maybe I'm missing something?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-1040) Ivy License Column not populating
Posted by "Kevin Gann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Gann updated IVY-1040:
----------------------------
Attachment: ivy.xml
Ivy.xml file defining dependencies.
> Ivy License Column not populating
> ---------------------------------
>
> Key: IVY-1040
> URL: https://issues.apache.org/jira/browse/IVY-1040
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.0
> Environment: Ubuntu 8.04. Java 1.6_10. x86.
> Reporter: Kevin Gann
> Attachments: ivy.xml, test-icsr-prototype-test-default.html
>
>
> Populating the License column in the Ivy report. If my assumption that if the POM has the license data in the directory used it would pull the license information?
> For example...
> I have the dependency defined...
> <dependency org="org.antlr" name="antlr" rev="3.1.1" />
> Which is coming from...
> http://repo1.maven.org/maven2/org/antlr/antlr/3.1.1/antlr-3.1.1.jar
> If I look at the HTTP directory I see the POM which contains the license information.
> http://repo2.maven.org/maven2/org/antlr/antlr/3.1.1/antlr-3.1.1.pom
> But when my report generates I don't see the license column populated. Maybe I'm missing something?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.