Re: Ant documentation
2018-03-02 7:44 GMT+01:00 Jan Matèrne (jhm) : > > > > > I made an attempt to convert the manual to HTML 5, the rationale > > > > being > > > > > that HTML 5 deprecates tt tag and recommends to replace it with > > > > > tags like code, kbd, samp and var, which could be used in a more > > > > consistent > > > > > way to achieve something closer to a semantic markup. > > > > > > > > > > I tried then to use the replacement tags as consistently as > > > > > possible in such a large body of text, but I realised that we > > > > > perhaps need a kind of a style guide. Would you like to discuss > > > > > it? Where would it best fit in the source code tree? > > > > > > > > > > > > > Isn't the HTML manual generated? Sure it's checked-in, but I > > thought > > > > there was a generation process. > > > > If that's the case (I may have dreamed it) then it's likely the > > > > generator that needs fixing, not the build product. --DD > > > > > > No. There were some experiments and maybe some pages were generated > > > during that experiment. > > > But the manual is a manual work. (double manual ;) > > > https://svn.apache.org/repos/asf/ant/sandbox/historical/xdocs/ > > > > > > > One may use xdoc and generate html with Doxia by calling its CLI. > > However, Ant sorely lacks a site generator on par with Maven site > > plugin. > > All generation requires a model to generate from. > AFAIK the site-plugin uses the pom for this purpose. > We don't have such a model in Ant. > Also I can't remember a wish for that. > Additionally I don't know any project (in my company) that uses these > sites. Maybe > they are useful for open source projects. > site plugin gets a lot of configuration from pom.xml, but there's site.xml, too. Perhaps if a wrapper of Doxia sitetools with a distinct skin would be used if it were available? Gintas
AW: Ant documentation
> > > > I made an attempt to convert the manual to HTML 5, the rationale > > > being > > > > that HTML 5 deprecates tt tag and recommends to replace it with > > > > tags like code, kbd, samp and var, which could be used in a more > > > consistent > > > > way to achieve something closer to a semantic markup. > > > > > > > > I tried then to use the replacement tags as consistently as > > > > possible in such a large body of text, but I realised that we > > > > perhaps need a kind of a style guide. Would you like to discuss > > > > it? Where would it best fit in the source code tree? > > > > > > > > > > Isn't the HTML manual generated? Sure it's checked-in, but I > thought > > > there was a generation process. > > > If that's the case (I may have dreamed it) then it's likely the > > > generator that needs fixing, not the build product. --DD > > > > No. There were some experiments and maybe some pages were generated > > during that experiment. > > But the manual is a manual work. (double manual ;) > > https://svn.apache.org/repos/asf/ant/sandbox/historical/xdocs/ > > > > One may use xdoc and generate html with Doxia by calling its CLI. > However, Ant sorely lacks a site generator on par with Maven site > plugin. All generation requires a model to generate from. AFAIK the site-plugin uses the pom for this purpose. We don't have such a model in Ant. Also I can't remember a wish for that. Additionally I don't know any project (in my company) that uses these sites. Maybe they are useful for open source projects. I don’t think that we should spend any effort into that. But Ant is an OS project - if you want to do a prototype you're welcome. Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user chinhodado commented on the issue: https://github.com/apache/ant-ivy/pull/68 Unrelated, but maybe you should consider enabling the issue tracker here on github. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy pull request #68: Why no new Ivy version yet?
Github user chinhodado closed the pull request at: https://github.com/apache/ant-ivy/pull/68 --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user sutchark commented on the issue: https://github.com/apache/ant-ivy/pull/68 Thanks for your help. P.S.: Maybe one pre-release test should download an extensive list of dependencies with Ivy and compare them to what Maven or Gradle is getting. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/68 Yes, it is. See the list of bug reports above. I'd say we have another blocker, speaking of releases. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user sutchark commented on the issue: https://github.com/apache/ant-ivy/pull/68 What is the naming sceme you suggested fixing?: `String pattern = destFolder + "/[organization]/[module]/[type]/[artifact]-[revision](-[classifier]).[ext]";` The dependency lwjgl-3.1.2.jar still gets lost, right? So this is a bug? --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/68 What you download is `lwjgl-3.1.2-natives-macos.jar`; the dependency `lwjgl-3.1.2.jar` gets lost. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user sutchark commented on the issue: https://github.com/apache/ant-ivy/pull/68 `http://central.maven.org/maven2/org/lwjgl/lwjgl/3.1.2/lwjgl-3.1.2.jar` --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/68 You get the correct name using pattern `"artifact]-[revision](-[classifier]).[ext]"` ð --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/68 This is another case of [IVY-1576](https://issues.apache.org/jira/browse/IVY-1576); maybe related to [IVY-1484](https://issues.apache.org/jira/browse/IVY-1484) and [IVY-1407](https://issues.apache.org/jira/browse/IVY-1407) and [IVY-1244](https://issues.apache.org/jira/browse/IVY-1244). --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user sutchark commented on the issue: https://github.com/apache/ant-ivy/pull/68 True. The JUnit3 part is strange. My example above wasn't with the current master but the ivy-2.4.0.jar. Maybe that's the reason. Ignoring the platform-specific wjgl jars is only one part of the problem. Please go in the .ivy cache and look at the content of for example: org/lwjgl/lwjgl/ 3.1.2/lwjgl-3.1.2.jar Here is the correct jar for content comparison: http://central.mav en.org/maven2/org/lwjgl/lwjgl/ 3.1.2/lwjgl-3.1.2.jar When you look at the content of the jar, it isn't identical with the same jar stored on maven central. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/68 Oh, I see. We're looking at the same result, except you somehow keep an older version of junit (in my case JUnit 3 is evicted). The bug is (as you stated) that only platform-specific wjgl jars are downloaded. Somehow the presence of classifier makes Ivy ignore the artifact withouth them. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user sutchark commented on the issue:
https://github.com/apache/ant-ivy/pull/68
I used the code below to download all dependencies.
You see the output at the very bottom. Here are the 13 direct compile
dependencies it should download:
https://mvnrepository.com/artifact/io.playn/playn-java-lwjgl/2.0
It only downloads some OSX jars for lwjgl. Also the content of those jars
is somehow wrong when you open them.
Here is the correct jar for content comparison: http://central.mav
en.org/maven2/org/lwjgl/lwjgl/ 3.1.2/lwjgl-3.1.2.jar
Very confusing.
The file ivy2.xml looks like this:
`
`
`import java.io.File;
import java.io.IOException;
import java.text.ParseException;
import java.util.List;
import org.apache.ivy.Ivy;
import org.apache.ivy.core.LogOptions;
import org.apache.ivy.core.module.descriptor.ModuleDescriptor;
import org.apache.ivy.core.module.id.ModuleRevisionId;
import org.apache.ivy.core.report.ResolveReport;
import org.apache.ivy.core.retrieve.RetrieveOptions;
import org.apache.ivy.core.settings.IvySettings;
public class IvyApiExperiments {
public static void main(String[] args) throws ParseException,
IOException {
IvySettings ivySettings = new IvySettings();
// Now let's set the basedir of the ivy settings to some
location
File baseDir = new File(".");
System.out.println("baseDir: " + baseDir.getAbsolutePath());
ivySettings.setBaseDir(baseDir);
// create an ivy instance
Ivy ivy = Ivy.newInstance(ivySettings);
// That's where my ivy-settings.xml is located
File ivySettingsXmlFile = new File("./ivysettings.xml");
System.out.println(ivySettingsXmlFile.getAbsolutePath());
// configure ivy to use the settings file
ivy.configure(ivySettingsXmlFile);
System.out.println("\n\n1. Define Dependencies\n\n");
// file containing the list of dependencies (ex: ivy.xml)
// File dependencyFile = new File("./ivy-2.0.xml");
File dependencyFile = new File("./ivy2.xml");
System.out.println("\n\n2. Resolve Dependencies\n\n");
// resolve the dependencies - Ivy returns a report of the
resolution
ResolveReport resolveReport = ivy.resolve(dependencyFile);
// check for errors (if any) during resolve
if (resolveReport.hasError()) {
List problems =
resolveReport.getAllProblemMessages();
if (problems != null && !problems.isEmpty()) {
StringBuffer errorMsgs = new StringBuffer();
for (String problem : problems) {
errorMsgs.append(problem);
errorMsgs.append("\n");
}
System.err.println("Errors encountered during
dependency resolution for package :");
System.err.println(errorMsgs);
}
} else {
System.out.println("Dependencies in file " +
dependencyFile + " were successfully resolved");
}
System.out.println("\n\n3. Retrieve Dependencies\n\n");
// Now that the dependencies have been resolved, let now
retrieve them
// Get the descriptor
ModuleDescriptor md = resolveReport.getModuleDescriptor();
// module revision id of the module whose dependencies were
resolved
ModuleRevisionId mRID = md.getModuleRevisionId();
// options that we pass to ivy instance for retrieve the
dependencies
RetrieveOptions retrieveOptions = new RetrieveOptions();
// folder to which we want the dependencies retrieved
File destFolder = new File("./retrieved");
// the Ivy pattern which will be used for retrieving the
dependencies
String pattern = destFolder +
"/[organization]/[module]/[type]/[artifact]-[revision].[ext]";
retrieveOptions.setDestIvyPattern(pattern);
// default logging option
retrieveOptions.setLog(LogOptions.LOG_DEFAULT);
// retrieve them!
int packagesRetrieved = ivy.retrieve(mRID, pattern
Re: Ant documentation
2018-03-01 10:43 GMT+01:00 Jan Matèrne (jhm) : > > > I made an attempt to convert the manual to HTML 5, the rationale > > being > > > that HTML 5 deprecates tt tag and recommends to replace it with tags > > > like code, kbd, samp and var, which could be used in a more > > consistent > > > way to achieve something closer to a semantic markup. > > > > > > I tried then to use the replacement tags as consistently as possible > > > in such a large body of text, but I realised that we perhaps need a > > > kind of a style guide. Would you like to discuss it? Where would it > > > best fit in the source code tree? > > > > > > > Isn't the HTML manual generated? Sure it's checked-in, but I thought > > there was a generation process. > > If that's the case (I may have dreamed it) then it's likely the > > generator that needs fixing, not the build product. --DD > > No. There were some experiments and maybe some pages were generated during > that experiment. > But the manual is a manual work. (double manual ;) > https://svn.apache.org/repos/asf/ant/sandbox/historical/xdocs/ > One may use xdoc and generate html with Doxia by calling its CLI. However, Ant sorely lacks a site generator on par with Maven site plugin. Gintas
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/68 What's missing? ``` $ java -jar build/artifact/jars/ivy.jar -dependency io.playn playn-java-lwjgl 2.0 :: loading settings :: url = jar:file:/Users/gintas/Projects/ant-ivy-asf/build/artifact/jars/ivy.jar!/org/apache/ivy/core/settings/ivysettings.xml :: resolving dependencies :: io.playn#playn-java-lwjgl-caller;working confs: [default] found io.playn#playn-java-lwjgl;2.0 in public found io.playn#playn-java-base;2.0 in public found io.playn#playn-core;2.0 in public found com.samskivert#pythagoras;1.4.3 in public found com.threerings#react;1.5.3 in public found com.googlecode.soundlibs#mp3spi;1.9.5-1 in public found com.googlecode.soundlibs#jlayer;1.0.1-1 in public found com.googlecode.soundlibs#tritonus-share;0.3.7-1 in public found org.java-websocket#Java-WebSocket;1.3.0 in public found org.lwjgl#lwjgl;3.1.2 in public found org.lwjgl#lwjgl-opengl;3.1.2 in public found org.lwjgl#lwjgl-glfw;3.1.2 in public found junit#junit;4.12 in default found org.hamcrest#hamcrest-core;1.3 in default ``` --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivy issue #68: Why no new Ivy version yet?
Github user sutchark commented on the issue: https://github.com/apache/ant-ivy/pull/68 Tested this with the latest release (2.4.0) and also a build of the latest master. Fetching all dependencies of: organisation="io.playn" module="playn-java-lwjgl" revision="2.0" Most of the dependencies are just fetched fine but it doesn't fetch all necessary dependencies from organisation='org.lwjgl' Tested this with Maven and Gradle. Both fetch the dependencies correctly. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivyde pull request #7: Fix IVYDE-386
Github user jonl-percsolutions-com closed the pull request at: https://github.com/apache/ant-ivyde/pull/7 --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivyde issue #7: Fix IVYDE-386
Github user jonl-percsolutions-com commented on the issue: https://github.com/apache/ant-ivyde/pull/7 @jaikiran Your fix is much better. I did not understand enough about the code to see whether or not it was intentional for those to be MenuManager objects or not. I have updated to the beta build with your pull request and can confirm that it fixes the issue I was seeing an all menus in eclipse are being built correctly. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Future of SVN repos
Oh yeah, it looks like gitbox isn't self serve yet. :( On 28 February 2018 at 13:35, Jan Matèrne (jhm) wrote: > Thanks for the reminder, Matt. So we could stay on ASF infrastructure. > https://selfserve.apache.org/ > but for git repos https://gitbox.apache.org/ > > Both forms require PMC-name, repo-name, repo-description, > commit-notification-list and github-notification list. > But while (for me) the selfserve-form seems to be fully functional, the > gitbox-form had no entries for the PMC listbox. > > > Jan > > > -Ursprüngliche Nachricht- > > Von: Matt Sicker [mailto:boa...@gmail.com] > > Gesendet: Mittwoch, 28. Februar 2018 19:50 > > An: Ant Developers List > > Betreff: Re: Future of SVN repos > > > > Creating new git repos on apache is self-serve, so it's just as easy as > > GitHub really (though you need to be a PMC member I think). > > > > On 28 February 2018 at 12:48, Jan Matèrne (jhm) > > wrote: > > > > > > > If we want to migrate the site repo, we should also think about > > > > > handling the sandbox. > > > > > > > > I think we just never migrated it because it simply wasn't used. > > > > Using a single git repository for several unrelated experiments > > > > doesn't sound very git-like. > > > > > > Yep. > > > We could migrate site to git and then close all svn repos (make them > > > read-only). > > > If required someone could create a local git repo for new "sandbox > > > experiments". Shareable via github and later moving to ASF > > > infrastructure if it changes to be more than an experiment. > > > > > > What do you think? > > > > > > > > > Jan > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional > > > commands, e-mail: dev-h...@ant.apache.org > > > > > > > > > > > > -- > > Matt Sicker > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > > -- Matt Sicker
AW: Ant nightly Jenkins job
sure Jan > -Ursprüngliche Nachricht- > Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com] > Gesendet: Donnerstag, 1. März 2018 12:50 > An: Ant Developers List > Betreff: Ant nightly Jenkins job > > Would it be OK if I redo the Ant nightly jenkins job[1] to be a bit > more useful and publish an actual nightly binary, for users to try out > if they wish to? > > [1] https://builds.apache.org/job/Ant_Nightly/ > > -Jaikiran > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional > commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Ant nightly Jenkins job
Would it be OK if I redo the Ant nightly jenkins job[1] to be a bit more useful and publish an actual nightly binary, for users to try out if they wish to? [1] https://builds.apache.org/job/Ant_Nightly/ -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivyde pull request #:
Github user twogee commented on the pull request: https://github.com/apache/ant-ivyde/commit/fc68846bbd7b18da1bb303db5e8a54f93692a2bd#commitcomment-27860034 Thanks :+1: --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[GitHub] ant-ivyde pull request #8: IVYDE-386 Fix ClassCastException
Github user asfgit closed the pull request at: https://github.com/apache/ant-ivyde/pull/8 --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant test failures on Java 9
On 2018-03-01, Gintautas Grigelionis wrote: > Build File: .../src/tests/antunit/taskdefs/copy-test.xml > Tests run: 26, Failures: 0, Errors: 2, Time elapsed: 8,59 sec Passes for me locally as well as on Jenkins https://builds.apache.org/view/A-D/view/Ant/job/Ant-Build-Matrix-master-Linux/OS=xenial,jdk=JDK%201.9%20(latest)/lastCompletedBuild/testReport/ Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
AW: Ant documentation
> > I made an attempt to convert the manual to HTML 5, the rationale > being > > that HTML 5 deprecates tt tag and recommends to replace it with tags > > like code, kbd, samp and var, which could be used in a more > consistent > > way to achieve something closer to a semantic markup. > > > > I tried then to use the replacement tags as consistently as possible > > in such a large body of text, but I realised that we perhaps need a > > kind of a style guide. Would you like to discuss it? Where would it > > best fit in the source code tree? > > > > Isn't the HTML manual generated? Sure it's checked-in, but I thought > there was a generation process. > If that's the case (I may have dreamed it) then it's likely the > generator that needs fixing, not the build product. --DD No. There were some experiments and maybe some pages were generated during that experiment. But the manual is a manual work. (double manual ;) https://svn.apache.org/repos/asf/ant/sandbox/historical/xdocs/ Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant documentation
On 2018-03-01, Dominique Devienne wrote: > On Thu, Mar 1, 2018 at 7:28 AM, Gintautas Grigelionis < > g.grigelio...@gmail.com> wrote: >> I tried then to use the replacement tags as consistently as possible in >> such a large body of text, but I realised that we perhaps need a kind of a >> style guide. Would you like to discuss it? Where would it best fit in the >> source code tree? I'm not convinced I want to have any kind of rules keep people from writing docs :-) > Isn't the HTML manual generated? Sure it's checked-in, but I thought there > was a generation process. This site is generated, the manual is not. We once had experiments creating the task manual pages via a doclet IIRC, but this never went far enough to be used in practice. Adding all the stuff that is part of the manual back into the classes would certainly require a lot of time, which was one of the problems. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant documentation
On Thu, Mar 1, 2018 at 7:28 AM, Gintautas Grigelionis < g.grigelio...@gmail.com> wrote: > I made an attempt to convert the manual to HTML 5, the rationale being that > HTML 5 deprecates tt tag and recommends to replace it with tags like code, > kbd, samp and var, which could be used in a more consistent way to achieve > something closer to a semantic markup. > > I tried then to use the replacement tags as consistently as possible in > such a large body of text, but I realised that we perhaps need a kind of a > style guide. Would you like to discuss it? Where would it best fit in the > source code tree? > Isn't the HTML manual generated? Sure it's checked-in, but I thought there was a generation process. If that's the case (I may have dreamed it) then it's likely the generator that needs fixing, not the build product. --DD
