Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It's OK not to have classes dir. #51

Closed
wants to merge 1 commit into from
Closed

Conversation

kohsuke
Copy link
Member

@kohsuke kohsuke commented Feb 17, 2017

... though rare. Previously, this would have caused 'no such directory' error during execution. With this change, now it creates an empty jar file.

@kohsuke
Copy link
Member Author

kohsuke commented Feb 17, 2017

@reviewbybees

@aheritier
Copy link
Member

🐝

@stephenc
Copy link
Member

🐜 if we don't have a classes directory can you auto-generate index.jelly from the Pom description?

@jglick
Copy link
Member

jglick commented Feb 17, 2017

Ah, good point. We should at a minimum print a warning if target/classes/index.jelly is missing—every plugin should have it.

I presume this is somehow related to jenkinsci/jenkins#2754 but @kohsuke is not giving any context.

This also solves the problem of 'empty class directory blowing up
MavenArchiver, which is why I started looking into this in the first
place.
@kohsuke
Copy link
Member Author

kohsuke commented Feb 17, 2017

l tried to generate index.jelly but packaging is a wrong moment to do it. jar has already been created and tests have already run.

I'll just put index.jelly manually instead of trying to be smart.

@kohsuke kohsuke closed this Feb 17, 2017
@jglick jglick deleted the empty-classes-dir branch February 21, 2017 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants